RE: Dump snapshot issue...

2009-05-07 Thread Marc Coyles
 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 13G 77G14%/home
/dev/da0s1d7.7G136K7.1G 0%/tmp
/dev/da0s1e9.7G5.6G3.3G63%/usr
/dev/da0s1f9.7G1.3G7.6G15%/var
/dev/da1s1d133G 40G 82G33%/backup
devfs  1.0K1.0K  0B   100%/var/named/dev
procfs 4.0K4.0K  0B   100%/proc


Marci


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


RE: Dump snapshot issue...

2009-05-06 Thread Marc Coyles
 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.
 

Dump is running as root via cron / initiated by hand.
ACLs not used.
Have removed all existing dump_snapshot files, and
have also removed and recreated all .snap directories.

S'now working fine for all mountpoints, except /home...

mksnap_ffs: Cannot create /home/.snap/dump_snapshot: Input/output error
dump: Cannot create /home/.snap/dump_snapshot: No such file or directory

It doesn't appear to proceed as normal either... as you can see below,
it ends the previous dump, starts the /home dump, gets an I/O error,
then proceeds straight to the /usr dump. The /home dump never gets
performed. If I remove the -L option, everything goes thru fine, but
complains about lack of -L flag...

  DUMP: DUMP IS DONE 
mksnap_ffs: Cannot create /home/.snap/dump_snapshot: Input/output error
dump: Cannot create /home/.snap/dump_snapshot: No such file or directory

  DUMP: Date of this level 0 dump: Wed May  6 08:30:31 2009
  DUMP: Date of last level 0 dump: the epoch
  DUMP: Dumping snapshot of /dev/da0s1e (/usr) to standard output


Fsck finds no errors on /home... point to note... mksnap_ffs CAN create
/home/.snap/dump_snapshot as I'm sat looking at the file, however, once
it's created it it's as tho it can't access it. The file is there, it
wasn't before I ran the script. It's created it as root:operator, perms
400. I can open it in pico, add content to it, and save it happily. So
I'm baffled!

M



___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Dump snapshot issue...

2009-05-06 Thread Jerry McAllister
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 ACLs, etc.
  
  And consider the permissions you're running dump with.
  
 
 Dump is running as root via cron / initiated by hand.
 ACLs not used.
 Have removed all existing dump_snapshot files, and
 have also removed and recreated all .snap directories.
 
 S'now working fine for all mountpoints, except /home...
 

Is /home really a separate file system on your system?
Or is it just a directory in another filesystem?

jerry


 mksnap_ffs: Cannot create /home/.snap/dump_snapshot: Input/output error
 dump: Cannot create /home/.snap/dump_snapshot: No such file or directory
 
 It doesn't appear to proceed as normal either... as you can see below,
 it ends the previous dump, starts the /home dump, gets an I/O error,
 then proceeds straight to the /usr dump. The /home dump never gets
 performed. If I remove the -L option, everything goes thru fine, but
 complains about lack of -L flag...
 
   DUMP: DUMP IS DONE 
 mksnap_ffs: Cannot create /home/.snap/dump_snapshot: Input/output error
 dump: Cannot create /home/.snap/dump_snapshot: No such file or directory
 
   DUMP: Date of this level 0 dump: Wed May  6 08:30:31 2009
   DUMP: Date of last level 0 dump: the epoch
   DUMP: Dumping snapshot of /dev/da0s1e (/usr) to standard output
 
 
 Fsck finds no errors on /home... point to note... mksnap_ffs CAN create
 /home/.snap/dump_snapshot as I'm sat looking at the file, however, once
 it's created it it's as tho it can't access it. The file is there, it
 wasn't before I ran the script. It's created it as root:operator, perms
 400. I can open it in pico, add content to it, and save it happily. So
 I'm baffled!
 
 M
 
 
 
 ___
 freebsd-questions@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Dump snapshot issue...

2009-05-05 Thread Marc Coyles
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
mksnap_ffs: Cannot create /home/.snap/dump_snapshot: Input/output error
dump: Cannot create /home/.snap/dump_snapshot: No such file or directory

/sbin/dump 0aLuf /dev/sa0 /tmp
dump: Cannot create /tmp/.snap/dump_snapshot: No such file or directory

/sbin/dump 0aLuf /dev/sa0 /usr
dump: Cannot create /usr/.snap/dump_snapshot: No such file or directory

/sbin/dump 0aLuf /dev/sa0 /var
dump: Cannot create /var/.snap/dump_snapshot: No such file or directory

/usr/bin/mt rewind


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...

Running 7.0-RELEASE-p11...

Any suggestions?

Marc A Coyles - Horbury School ICT Support Team
Mbl: 07850 518106
Land: 01924 282740 ext 730
Helpdesk: 01924 282740 ext 2000
 



___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Dump snapshot issue...

2009-05-05 Thread Andrew Wright

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 directory


You probably have not created the .snap directory in the root of the
filesystem.


From the dump(8) man page:

If the .snap directory does not exist in the root of the
file system being dumped, a warning will be issued and the
dump will revert to the standard behavior.  This problem
can be corrected by creating a .snap directory in the root
of the file system to be dumped; its owner should be
``root'', its group should be ``operator'', and its mode
should be ``0770''.

A.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


RE: Dump snapshot issue...

2009-05-05 Thread Marc Coyles
 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


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Dump snapshot issue...

2009-05-05 Thread Lowell Gilbert
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 file or directory

 /sbin/dump 0aLuf /dev/sa0 /home
 mksnap_ffs: Cannot create /home/.snap/dump_snapshot: Input/output error
 dump: Cannot create /home/.snap/dump_snapshot: No such file or directory

 /sbin/dump 0aLuf /dev/sa0 /tmp
 dump: Cannot create /tmp/.snap/dump_snapshot: No such file or directory

 /sbin/dump 0aLuf /dev/sa0 /usr
 dump: Cannot create /usr/.snap/dump_snapshot: No such file or directory

 /sbin/dump 0aLuf /dev/sa0 /var
 dump: Cannot create /var/.snap/dump_snapshot: No such file or directory

 /usr/bin/mt rewind


 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...

 Running 7.0-RELEASE-p11...

 Any suggestions?

Wow.  That's strange.  I've never seen anything like it.  

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.

Good luck.
-- 
Lowell Gilbert, embedded/networking software engineer, Boston area
http://be-well.ilk.org/~lowell/
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org