The snapshot app went through a long gather & squash procedure, and flashed a message popup indicating successful completion. There is only an empty .md5 file in the /home/snapshot directory.

/var/log/antixsnapshot_errors.log says:

"kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec]
cp: cannot stat `/etc/udev/rules.d/90-fstab-automount.rules.live': No such file or directory
ls: cannot access /home/snapshot/*.iso: No such file or directory

- - -
I'm totally at a loss about this message.
It would be nice to make snapshots of my installation.
I've been very happy with antix over the last few months, and am
slowly migrating much work/projects over from Win & Mac to antiX
Thanks
Gray

I ran an antixsnapshot last night and had no issues. 1.5GB in size.

Graybyrd - which version of antiX are you running? Is there an /etc/udev/rules.d/90-fstab-automount.rules.live before you create the snapshot?

anticapitalista: here's the system info, and a peek at the /etc/udev/rules.d/ directory contents:

---(NOTE:)---
System is current as of 4/13/2013 using"apt-get update && apt-get dist-upgrade" with repository listings set to"testing";"smxi" script has been run recently using various update & cleaning functions.

################### PC INFORMATION - system #####################
################### Press CTRL + C to exit #####################

System: Host: antiXcompaq Kernel: 3.5.0-antix.2-486-smp i686 (32 bit)
Desktop: IceWM 1.3.7 Distro: antiX-full Edelweißpiraten 06 August 2012

Processes: CPU - % used - top 10 active
1: cpu: 21.0% command: yad pid: 5383
2: cpu: 8.7% command: iceweasel pid: 3305
3: cpu: 3.3% command: X pid: 2494
4: cpu: 1.0% command: dropbox pid: 3203
5: cpu: 0.9% command: roxterm pid: 4135
6: cpu: 0.8% command: conky pid: 3047
7: cpu: 0.3% command: leafpad pid: 4460
8: cpu: 0.1% command: icewm pid: 3014
9: cpu: 0.1% command: rox pid: 3012
10: cpu: 0.1% command: python pid: 2883

Info: Processes: 95 Uptime: 14 min Memory: 341.5/1254.9MB Client: Shell (inxi-gui) inxi: 1.8.45




$ cd /etc/udev/rules.d/
graybyrd@antiXcompaq:/etc/udev/rules.d
$ ls
70-persistent-cd.rules 70-persistent-net.rules 99-usbstorage.rules.unused

$ cat 70-persistent-cd.rules
# This file was automatically generated by the /lib/udev/write_cd_rules
# program, run by the cd-aliases-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single
# line, and set the $GENERATED variable.

# ATAPI_DVD_A_DH20A4P (pci-0000:00:1f.1-scsi-0:0:0:0)

---(etc, etc)---

$ cat 70-persistent-net.rules
# This file was automatically generated by the /lib/udev/write_net_rules
# program, run by the persistent-net-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single
# line, and change only the value of the NAME= key.

# PCI device 0x10ec:/sys/devices/pci0000:00/0000:00:1e.0/0000:01:0f.0 (8139too)

---(etc, etc)---

$ cat 99-usbstorage.rules.unused
KERNEL!="sd*[1-9]*", GOTO="exit"

# Import FS infos
SUBSYSTEMS=="usb", IMPORT{program}="/sbin/blkid -o udev -p %N"

# Get a label if present, otherwise specify one
SUBSYSTEMS=="usb", ENV{ID_FS_LABEL}!="", ENV{dir_name}="%E{ID_FS_LABEL}"
SUBSYSTEMS=="usb", ENV{ID_FS_LABEL}=="", ENV{dir_name}="usb-%k"

# Global mount options
SUBSYSTEMS=="usb", ACTION=="add", ENV{pmount_options}="--noatime"

---(etc, etc)---

Make a file /etc/udev/rules.d/90-fstab-automount.rules.live with this as contents.
and try again.

BTW that was a bug you found and is now fixed for next antixsnapshot deb upgrade.

Thanks for the reply & suggestion. Made the file entry as suggested:

$ cat 90-fstab-automount.rules.live
ACTION=="add|change|remove",SUBSYSTEM=="block",KERNEL=="sd*" RUN+="/bin/sh -c '/sbin/make-fstab'"
graybyrd@antiXcompaq:/etc/udev/rules.d

Ran"Antixsnapshot" ... took over an hour. YAD reported completion. There was another empty .md5 file in the /home/snapshot directory. No .iso snapshot file.

Error log for Antixsnapshot:

$ cat antixsnapshot_errors.log
kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec]
ls: cannot access /home/snapshot/*.iso: No such file or directory
8152 blocks
mkdir: cannot create directory `3.5.0-antix.2-486-smp': File exists
.
./run
./run/udev
./lib
./lib/libc.so.6
./lib/modules
./lib/modules/3.5.0-antix.2-486-smp

[---snip long file listing---]

./dev/tty1
./dev/mdev.seq
./tmp
8152 blocks
/usr/local/bin/antixsnapshot-gui: line 276: 18946 Terminated yad --width 300 --title"Copying filesystem..." --progress --pulsate
rm: cannot remove `/home/work/new-iso/snapshot*': No such file or directory
/usr/local/bin/antixsnapshot-gui: line 317: 20953 Terminated yad --width 300 --title"Squashing filesystem..." --progress --pulsate
I: -input-charset not specified, using utf-8 (detected in locale settings)
File ./antiX/linuxfs is larger than 4GiB-1.
-allow-limited-size was not specified. There is no way do represent this file size. Aborting.
isohybrid: could not open file `/home/snapshot/snapshot-20130414_1343.iso': No such file or directory
md5sum: /home/snapshot/snapshot-20130414_1343.iso: No such file or directory
/usr/local/bin/antixsnapshot-gui: line 325: 11168 Terminated yad --title"Creating CD image file..." --progress --pulsate

(yad:11178): GLib-CRITICAL **: g_source_remove: assertion `tag > 0' failed
/usr/local/bin/antixsnapshot-gui: line 341: 11178 Terminated yad --title"Cleaning..." --progress --pulsate
kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec]
graybyrd@antiXcompaq:/var/log
$

Graybyrd wrote:File ./antiX/linuxfs is larger than 4GiB-1.
-allow-limited-size was not specified. There is no way do represent this file size. Aborting.

I think this is the main problem. That's pretty big for a squashfs file. It's 6 times larger than antiX-full. What is the output of"df -h"?

Have you installed a lot of packages and/or large data files?

Understand. No filesize limit was mentioned; I've added considerable to the install since I'm trying to migrate from Mac/Win to Antix for daily use. (I should note that I was familiar with tools to keep 'cruft' cleaned out of WinXP/7 and Mac OSX. Linux is a horse of a different color; a very complex structure. I'm not sure about house-cleaning tools here other than 'apt-get autoclean' etc. and a few rather mysterious 'smxi' options.)

It is always good to push the envelope.


========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://refracta.freeforums.org/squashfs-larger-than-4gb-t172.html"
linktext was:"This refracta thread"
====================================
has a work-around you can try. The genisoimage man page warns:

-allow-limited-size
When processing files larger than 2GiB which cannot be easily repre-
sented in ISO9660, add them with a shrunk visible file size to
ISO9660 and with the correct visible file size to the UDF system.
The result is an inconsistent filesystem and users need to make sure
that they really use UDF rather than ISO9660 driver to read a such
disk. Implies enabling -udf.

Thinking aloud here:
It is also (theoretically) possible to split the squashfs file (that's the file that's too big) into chunks and then play some tricks to mount all of those chunks together but this is probably not something for you to try at home. Antix is focused on being small and fast so we will probably not be adding this feature anytime soon.

We could possibly offer an option that creates a LiveUSB directly instead of making an iso file. This approach would not have the filesize limitation you ran into. We should probably also warn users if it looks like their system is too big to fit into an iso.

Thank you. Problems noted. I do really really wish a way to clone the antiX install to a USB thumb drive.

One note: this antiX install is a delight. Rock solid, fast, flexible, and so far nothing has broken despite continuing dist-upgrades. Thanks to all involved. It's appreciated.

There are several scripts in /usr/local/bin that should already do this. I don't know which is the best one to use but I'm sure other people here can tell you which one to use and how to use it. I almost never bother with antiX LiveCDs. I always make antiX LiveUSBs.

I think most of the changes in antiX-13 will be new features for the LiveUSB. Over the last few years, we've put a lot of development work into the antiX LiveUSB but the antiX-12 LiveUSB is still quite good.

Graybyrd,

if you want to give it another try, edit this line in /etc/antixsnapshot.conf

save_work="no" to save_work="yes"

This will save all the files in work, even if the script fails again.

Graybyrd, if antiCapitalista's suggestion works then I can easily help you make a LiveUSB with the saved information. The only size limit will be the size of the usb device.

if you want to give it another try, edit this line in /etc/antixsnapshot.conf

save_work="no" to save_work="yes"

Done ... and Done!

First, I moved a bunch of download stuff off to a DVD, to reduce the overburden. Then changed the script to save_work="yes"; ran antixsnapshot, and got an iso file in the"home/snapshot" directory of 1.7 gb.

The"home/work" folder contains a whole lot of stuff I don't understand, but that's ok. (It must mean something to somebody ... )

Burned the resulting snapshot.iso to a DVD-RW using 'simpleburn' and rebooted from that. The startup screen freaked me out ... with a huge warning that my 'puter is 32-bit and won't boot off a 64-bit OS ??? (WTF is that about?)

But after moving out of that box and choosing the first startup option, I was delighted to see my familiar wallpaper screen and everything duplicated to mirror my antiX install. Nice! I've not tried it yet, but I'm assuming I can move that snapshot.iso to a USB thumb drive and have a clone copy if some dist-upgrade happens to bork my HD install... but I haven't tried that yet.

Now I need to learn the mystery of editing Grub ... which I must say, causes mild panic. I've lost several installs of Linux in the past due to some weird grub update glitch that came through apt-get updates, and it also took out a full Windows XP install with a helluva lot of software and personal data ... that soured me on Linux for a year! So when I say that antiX has been rock-solid and very satisfactory, I'm not just blowing smoke.

Thanks for the help, to all of you.
Gray

P.S. BitJam -- if you have a neat way of cloning or duping the install to a USB thumb drive, say 16 or 32 gb size, I'm here to listen !