Re: dump(8) + UFS2
Hello :-) I just (20:00 CET) did a new 'make world' on my current-slice and I'm happy to report that dump(8) is working perfectly now, even on UFS2. It's performing 'snapshots' on mounted filesystems for backup and additionally seems to be somewhat (at least) faster... Great Job! Thanks a lot! -- Ciao/BSD - Matthias Matthias Schuendehuette msch [at] snafu.de, Berlin (Germany) Powered by FreeBSD 5.0-CURRENT To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: dump(8) + UFS2
On Sat, 30 Nov 2002, Manfred Antar wrote: At 10:56 AM 11/30/2002 -0200, Daniel C. Sobral wrote: Well, I once restored something to UFS2 (converting my partitions...). It was quite funny to see 102.7% was complete, and it would end in 0 (minutes, one assume). Here are further messages from console when trying to dump UFS2 It seems like a controller error also: (da0:ahc0:0:0:0): Unretryable error (da0:ahc0:0:0:0): READ(10). CDB: 28 0 b3 9b 97 60 0 0 1 0 (da0:ahc0:0:0:0): CAM Status: SCSI Status Error (da0:ahc0:0:0:0): SCSI Status: Check Condition (da0:ahc0:0:0:0): ILLEGAL REQUEST asc:21,0 (da0:ahc0:0:0:0): Logical block address out of range field replaceable unit: 3: Command byte 2 bit 7 is invalid This is the dump program's fault still. The controller is just saying that block is way out of range, unless you have a 1.5 TB disk. ;-) -Nate To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: dump(8) + UFS2
Matthias Schuendehuette wrote: Hello, it seems to me that 'dump' (8) is not able to dump UFS2 Filesystems. First it shows an extraordirarily large number of estimated tape blocks for my tiny /var-partition and after that it dumps core while trying to dump my not so tiny /usr partition. Is this a known issue? Are there any recommendations how to backup UFS2 filesystems reliably? Well, I once restored something to UFS2 (converting my partitions...). It was quite funny to see 102.7% was complete, and it would end in 0 (minutes, one assume). -- Daniel C. Sobral(8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] Fundamentalist Debianites, core children of the Linuxen sounds like it could come from the Book of Mormon, or Tolkien on a bad day... To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: dump(8) + UFS2
At 10:56 AM 11/30/2002 -0200, Daniel C. Sobral wrote: Matthias Schuendehuette wrote: Hello, it seems to me that 'dump' (8) is not able to dump UFS2 Filesystems. First it shows an extraordirarily large number of estimated tape blocks for my tiny /var-partition and after that it dumps core while trying to dump my not so tiny /usr partition. Is this a known issue? Are there any recommendations how to backup UFS2 filesystems reliably? Well, I once restored something to UFS2 (converting my partitions...). It was quite funny to see 102.7% was complete, and it would end in 0 (minutes, one assume). I just converted my /var and /usr partitions to UFS2 on an i386 machine and tried to do a dump of /var (500mb -- 37mb used) (disklabel)594}dump 0fua /dev/nsa0 /dev/da0s1e DUMP: Date of this level 0 dump: Sat Nov 30 10:16:44 2002 DUMP: Date of last level 0 dump: the epoch DUMP: Dumping /dev/da0s1e (/var) to /dev/nsa0 DUMP: mapping (Pass I) [regular files] DUMP: mapping (Pass II) [directories] DUMP: read error from /dev/da0s1e: Input/output error: [block -7236860474136607228]: count=8192 DUMP: read error from /dev/da0s1e: Input/output error: [sector -7236860474136607228]: count=512 DUMP: read error from /dev/da0s1e: Input/output error: [sector -7236860474136607227]: count=512 DUMP: read error from /dev/da0s1e: Input/output error: [sector -7236860474136607226]: count=512 DUMP: read error from /dev/da0s1e: Input/output error: [sector -7236860474136607225]: count=512 DUMP: read error from /dev/da0s1e: Input/output error: [sector -7236860474136607224]: count=512 DUMP: read error from /dev/da0s1e: Input/output error: [sector -7236860474136607223]: count=512 DUMP: read error from /dev/da0s1e: Input/output error: [sector -7236860474136607222]: count=512 DUMP: read error from /dev/da0s1e: Input/output error: [sector -7236860474136607221]: count=512 DUMP: read error from /dev/da0s1e: Input/output error: [sector -7236860474136607220]: count=512 DUMP: read error from /dev/da0s1e: Input/output error: [sector -7236860474136607219]: count=512 DUMP: read error from /dev/da0s1e: Input/output error: [sector -7236860474136607218]: count=512 DUMP: read error from /dev/da0s1e: Input/output error: [sector -7236860474136607217]: count=512 DUMP: read error from /dev/da0s1e: Input/output error: [sector -7236860474136607216]: count=512 DUMP: read error from /dev/da0s1e: Input/output error: [sector -7236860474136607215]: count=512 DUMP: read error from /dev/da0s1e: Input/output error: [sector -7236860474136607214]: count=512 DUMP: read error from /dev/da0s1e: Input/output error: [sector -7236860474136607213]: count=512 DUMP: corrupted directory, inumber 5169 DUMP: read error from /dev/da0s1e: Input/output error: [block -3126763002007185064]: count=8192 DUMP: read error from /dev/da0s1e: Input/output error: [sector -3126763002007185064]: count=512 DUMP: read error from /dev/da0s1e: Input/output error: [sector -3126763002007185063]: count=512 DUMP: read error from /dev/da0s1e: Input/output error: [sector -3126763002007185062]: count=512 DUMP: read error from /dev/da0s1e: Input/output error: [sector -3126763002007185061]: count=512 DUMP: read error from /dev/da0s1e: Input/output error: [sector -3126763002007185060]: count=512 DUMP: read error from /dev/da0s1e: Input/output error: [sector -3126763002007185059]: count=512 DUMP: read error from /dev/da0s1e: Input/output error: [sector -3126763002007185058]: count=512 DUMP: read error from /dev/da0s1e: Input/output error: [sector -3126763002007185057]: count=512 DUMP: read error from /dev/da0s1e: Input/output error: [sector -3126763002007185056]: count=512 DUMP: read error from /dev/da0s1e: Input/output error: [sector -3126763002007185055]: count=512 DUMP: read error from /dev/da0s1e: Input/output error: [sector -3126763002007185054]: count=512 DUMP: read error from /dev/da0s1e: Input/output error: [sector -3126763002007185053]: count=512 DUMP: read error from /dev/da0s1e: Input/output error: [sector -3126763002007185052]: count=512 DUMP: read error from /dev/da0s1e: Input/output error: [sector -3126763002007185051]: count=512 DUMP: read error from /dev/da0s1e: Input/output error: [sector -3126763002007185050]: count=512 DUMP: read error from /dev/da0s1e: Input/output error: [sector -3126763002007185049]: count=512 DUMP: corrupted directory, inumber 5169 DUMP: corrupted directory, inumber 5169 DUMP: corrupted directory, inumber 5596 DUMP: read error from /dev/da0s1e: Input/output error: [block -8093102966837667782]: count=8192 DUMP: More than 32 block read errors from /dev/da0s1e DUMP: This is an unrecoverable error. DUMP: Do you want to attempt to continue?: (yes or no) no DUMP: The ENTIRE dump is aborted. I guess dump is not ready for UFS2 == || [EMAIL PROTECTED] || || Ph. (415) 681-6235 ||
Re: dump(8) + UFS2
At 10:56 AM 11/30/2002 -0200, Daniel C. Sobral wrote: Matthias Schuendehuette wrote: Hello, it seems to me that 'dump' (8) is not able to dump UFS2 Filesystems. First it shows an extraordirarily large number of estimated tape blocks for my tiny /var-partition and after that it dumps core while trying to dump my not so tiny /usr partition. Is this a known issue? Are there any recommendations how to backup UFS2 filesystems reliably? Well, I once restored something to UFS2 (converting my partitions...). It was quite funny to see 102.7% was complete, and it would end in 0 (minutes, one assume). Here are further messages from console when trying to dump UFS2 It seems like a controller error also: (da0:ahc0:0:0:0): Unretryable error (da0:ahc0:0:0:0): READ(10). CDB: 28 0 b3 9b 97 60 0 0 1 0 (da0:ahc0:0:0:0): CAM Status: SCSI Status Error (da0:ahc0:0:0:0): SCSI Status: Check Condition (da0:ahc0:0:0:0): ILLEGAL REQUEST asc:21,0 (da0:ahc0:0:0:0): Logical block address out of range field replaceable unit: 3: Command byte 2 bit 7 is invalid Manfred == || [EMAIL PROTECTED] || || Ph. (415) 681-6235 || == To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: dump(8) + UFS2
On Sat, 30 Nov 2002, Manfred Antar wrote: I guess dump is not ready for UFS2 I just have made dump and restore of my 3GB UFS2 /usr partition and did not experience any problems with that. Working on -CURRENT from Nov 24th. -- -- wrzask --= v =-- Winfried --=-- GG# 3838383 --=-- JS500-RIPE -- -- [EMAIL PROTECTED] --- [EMAIL PROTECTED] --===-- http://violent.dream.vg/ --- --= Ride the wild wind - push the envelope, don't sit on the fence, --- -- Ride the wild wind - live life on the razor's edge! =-- Queen -- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: dump(8) + UFS2
On Saturday 30 November 2002 23:24, you wrote: On Sat, 30 Nov 2002, Manfred Antar wrote: I guess dump is not ready for UFS2 I just have made dump and restore of my 3GB UFS2 /usr partition and did not experience any problems with that. Working on -CURRENT from Nov 24th. Sure you dumped an UFS2 filesystem? Here's my try: root@current - /root 104 # uname -a FreeBSD current.best-eng.de 5.0-CURRENT FreeBSD 5.0-CURRENT #3: Thu Nov 28 21:59:11 CET 2002 [EMAIL PROTECTED]:/disk/obj/usr/src/sys/CURRENT i386 root@current - /root 103 # dump 0af /dev/nsa0 /usr DUMP: Date of this level 0 dump: Sat Nov 30 23:50:24 2002 DUMP: Date of last level 0 dump: the epoch DUMP: Dumping /dev/da3s1g (/usr) to /dev/nsa0 DUMP: mapping (Pass I) [regular files] DUMP: mapping (Pass II) [directories] DUMP: SIGSEGV: ABORTING! Speicherschutzverletzung (core dumped) Or is it a SCSI-problem? Did you dump from an ATA or SCSI-Disk? To an ATA or SCSI tape-device? Astonishing... -- Ciao/BSD - Matthias Matthias Schuendehuette msch [at] snafu.de, Berlin (Germany) Powered by FreeBSD 5.0-CURRENT To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: dump(8) + UFS2
On Sat, 30 Nov 2002, Matthias Schuendehuette wrote: I just have made dump and restore of my 3GB UFS2 /usr partition and did not experience any problems with that. Working on -CURRENT from Nov 24th. Sure you dumped an UFS2 filesystem? Here's my try: root@current - /root 104 # uname -a FreeBSD current.best-eng.de 5.0-CURRENT FreeBSD 5.0-CURRENT #3: Thu Nov 28 21:59:11 CET 2002 [EMAIL PROTECTED]:/disk/obj/usr/src/sys/CURRENT i386 Hm, this is weird. I'm sure I have dumped an UFS2 filesystem earlier and it worked. Now I get similar error messages as you. Yes, I'm absolutely sure that the filesystem was UFS2 - played with extattrctl on it, checked it with dumpfs and was not able to mount it under -STABLE. dump utility is exacly the same (except that it now resides on a different disk). The filesystem after restore does not seem to be corrupted in any way (well, except that linux-*-jdk-* stuff SEGVs - kinda weird). This thing gets spooky a bit.. ;) Both my disks are IDEs, if that matters in any way. -- -- wrzask --= v =-- Winfried --=-- GG# 3838383 --=-- JS500-RIPE -- -- [EMAIL PROTECTED] --- [EMAIL PROTECTED] --===-- http://violent.dream.vg/ --- --= Ride the wild wind - push the envelope, don't sit on the fence, --- -- Ride the wild wind - live life on the razor's edge! =-- Queen -- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: dump(8) + UFS2
On Sun, 1 Dec 2002, Jan Srzednicki wrote: Hm, this is weird. I'm sure I have dumped an UFS2 filesystem earlier and it worked. Now I get similar error messages as you. Yes, I'm absolutely sure that the filesystem was UFS2 - played with extattrctl on it, checked it with dumpfs and was not able to mount it under -STABLE. dump utility is exacly the same (except that it now resides on a different disk). The filesystem after restore does not seem to be corrupted in any way (well, except that linux-*-jdk-* stuff SEGVs - kinda weird). This thing gets spooky a bit.. ;) Both my disks are IDEs, if that matters in any way. Erm, s/extattrctl/setextattr and getextattr/. -- -- wrzask --= v =-- Winfried --=-- GG# 3838383 --=-- JS500-RIPE -- -- [EMAIL PROTECTED] --- [EMAIL PROTECTED] --===-- http://violent.dream.vg/ --- --= Ride the wild wind - push the envelope, don't sit on the fence, --- -- Ride the wild wind - live life on the razor's edge! =-- Queen -- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
