Is /home really a separate file system on your system?
Or is it just a directory in another filesystem?
df -h output:
Filesystem SizeUsed Avail Capacity Mounted on
/dev/da0s1a3.9G351M3.2G10%/
devfs 1.0K1.0K 0B 100%/dev
/dev/da0s1g 98G
One thing you should try is to remove the dump_snapshot files,
because
they are supposed to be unlinked when the dump starts anyway, so
they
shouldn't be sticking around.
Also, look for file flags on the directories, or ACLs, etc.
And consider the permissions you're running dump with.
On Wed, May 06, 2009 at 10:01:36AM +0100, Marc Coyles wrote:
One thing you should try is to remove the dump_snapshot files,
because
they are supposed to be unlinked when the dump starts anyway, so
they
shouldn't be sticking around.
Also, look for file flags on the directories, or
I've got a script that dumps various filesystems to tape for me, but
I've always had an issue whenever I've used the -L option... see below:
/usr/bin/mt rewind
/sbin/dump 0aLuf /dev/sa0 /
dump: Cannot create //.snap/dump_snapshot: No such file or directory
/sbin/dump 0aLuf /dev/sa0 /home
On Tue, 5 May 2009, Marc Coyles wrote:
I've got a script that dumps various filesystems to tape for me, but
I've always had an issue whenever I've used the -L option... see below:
/usr/bin/mt rewind
/sbin/dump 0aLuf /dev/sa0 /
dump: Cannot create //.snap/dump_snapshot: No such file or
You probably have not created the .snap directory in the root of
the filesystem.
Like I said...
The .snap folders exist at all points, are set to root:operator,
with perms 770... The dump_snapshot files seem to be present, albeit
0 bytes, root:operator, perms 400...
Marc
Marc Coyles mcoy...@horbury.wakefield.sch.uk writes:
I've got a script that dumps various filesystems to tape for me, but
I've always had an issue whenever I've used the -L option... see below:
/usr/bin/mt rewind
/sbin/dump 0aLuf /dev/sa0 /
dump: Cannot create //.snap/dump_snapshot: No such
