Re: 8.0-RC3 USB lock up on mounting two partitions from one USB drive
Hi, I'm not sure if this is an USB issue or not. If you get READ/WRITE errors and the drive simply dies then it might be the case. Else it is a system issue. There are quirks for mass storage which you can add to sys/dev/usb/storage/umass.c . --HPS On Wednesday 18 November 2009 08:33:07 Guojun Jin wrote: Did newfs on those partition and made things worsen -- restore completely fails: (I had experienced another similar problem on an IDE, which works well for 6.4 and 7.2, but 8.0.) This dirve works fine under FreeBSD 6.4. Is something new in 8.0 making disk partition schema changed? g_vfs_done():da0s3d[READ(offset=98304, length=16384)]error = 6 g_vfs_done():da0s3d[WRITE(offset=192806912, length=16384)]error = 6 fopen: Device not configured cannot create save file ./restoresymtable for symbol table abort? [yn] (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0xa, scs i status == 0x0 (da0:umass-sim0:0:0:0): removing device entry ugen1.2: DMI at usbus1 umass0: DMI Ultra HDD, class 0/0, rev 2.00/1.19, addr 2 on usbus1 umass0: SCSI over Bulk-Only; quirks = 0x umass0:0:0:-1: Attached to scbus0 da0 at umass-sim0 bus 0 target 0 lun 0 da0: DMI Ultra HDD 1.19 Fixed Direct Access SCSI-0 device da0: 40.000MB/s transfers da0: 114473MB (234441648 512 byte sectors: 255H 63S/T 14593C) Device da0s3d went missing before all of the data could be written to it; expect data loss. 99 23:19 sysinstall 100 23:20 newfs /dev/da0s3d 101 23:20 newfs /dev/da0s3e 102 23:21 mount /dev/da0s3d /mnt 103 23:21 cd /mnt 104 23:21 dump -0f - /home | restore -rf - 105 23:27 history 15 -Original Message- From: Guojun Jin Sent: Tue 11/17/2009 11:05 PM To: freebsd-stable@freebsd.org Cc: questi...@freebsd.org; freebsd-...@freebsd.org Subject: 8.0-RC3 USB lock up on mounting two partitions from one USB drive When mounting two partitions from a USB dirve, it can cause the drive access lock up for a long time. Details: Terminal 1 -- term1# mount /dev/da0s3d /mnt term1# cd /mnt ; rm -fr * when rm starts, go to terminal 2 and do: term2# mount /dev/da0s3e /dist ### this will hanging for a long time and USB hard drive activity light is off. After more than 1-2 minutes, mount returns, and the drive activity light is blinking, thus removing is going on. term2# ls /dist ### this will cause dUSB dirve hanging again -- no avtivity. Similarly, ls will finish in a couple of miniutes or longer, the rm command continues; but for a while, the drive activity will stop again. Reboot machine, repeat the above steps, and result will be the same. Reboot machine again, and just mount one partition, then doing rm -rf * without involve the second partition, rm will finish quickly. Has anyone obseved this behave on 8.0-RC? -Jin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 8.0-RC3 USB lock up on mounting two partitions from one USB drive
On Wed, Nov 18, 2009 at 12:13:32PM +0100, Hans Petter Selasky wrote: I'm not sure if this is an USB issue or not. If you get READ/WRITE errors and the drive simply dies then it might be the case. Else it is a system issue. The OP should be able to use smartmontools to obtain SMART stats from the SATA drive within the USB enclosure. The command will be somewhat funky, given that the drive is ATA but is mapped through CAM on FreeBSD and appears as a daX disk. I believe the following should work, but I have no way to test: smartctl --device=ata -a /dev/da0 You should check your console logs (dmesg) before and after running this command, as there may be sense key errors from CAM which can help determine if SMART is passed through or not. There's mention in the smartctl man page of a device type called sat which is an ATA-SCSI emulation layer, but I believe it's the Linux equivalent of our CAM. Recent (in the past ~24 hours) commits to the RELENG_8 branch might provide native capability for smartctl to work without the --type argument, since mav@ has been improving the CAM layer to work with ATA disks. -- | Jeremy Chadwick j...@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 8.0-RC3 USB lock up on mounting two partitions from one USB drive
Jeremy Chadwick wrote: On Wed, Nov 18, 2009 at 12:13:32PM +0100, Hans Petter Selasky wrote: I'm not sure if this is an USB issue or not. If you get READ/WRITE errors and the drive simply dies then it might be the case. Else it is a system issue. The OP should be able to use smartmontools to obtain SMART stats from the SATA drive within the USB enclosure. The command will be somewhat funky, given that the drive is ATA but is mapped through CAM on FreeBSD and appears as a daX disk. I believe the following should work, but I have no way to test: smartctl --device=ata -a /dev/da0 You should check your console logs (dmesg) before and after running this command, as there may be sense key errors from CAM which can help determine if SMART is passed through or not. There's mention in the smartctl man page of a device type called sat which is an ATA-SCSI emulation layer, but I believe it's the Linux equivalent of our CAM. Recent (in the past ~24 hours) commits to the RELENG_8 branch might provide native capability for smartctl to work without the --type argument, since mav@ has been improving the CAM layer to work with ATA disks. Does not work for my external Seagate FreeAgent Go 500G USB2.0 drive %smartctl -a /dev/da0 smartctl version 5.38 [i386-portbld-freebsd8.0] Copyright (C) 2002-8 Bruce Allen Home page is http://smartmontools.sourceforge.net/ Device: Seagate FreeAgent GoVersion: 102D Device type: disk Local Time is: Wed Nov 18 21:22:01 2009 KRAT Device does not support SMART Error Counter logging not supported Device does not support Self Test logging %smartctl --device=ata /dev/da0 smartctl version 5.38 [i386-portbld-freebsd8.0] Copyright (C) 2002-8 Bruce Allen Home page is http://smartmontools.sourceforge.net/ Smartctl: Device Read Identity Failed (not an ATA/ATAPI device) A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options. %smartctl --device=ata -T permissive /dev/da0 smartctl version 5.38 [i386-portbld-freebsd8.0] Copyright (C) 2002-8 Bruce Allen Home page is http://smartmontools.sourceforge.net/ Smartctl: Device Read Identity Failed (not an ATA/ATAPI device) SMART support is: Ambiguous - ATA IDENTIFY DEVICE words 82-83 don't show if SMART supported. A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
RE: 8.0-RC3 USB lock up on mounting two partitions from one USB drive
It looks like a system issue since it also happens to the SATA drive. The USB drive seems having more difficulty. I will back up rest partitions, Then redo the slice and partition to see if problem goes away. If so, then 8.0-R has a backward compatibility issue on the partition table or format to older FreeBSD release. -Original Message- From: Hans Petter Selasky [mailto:hsela...@c2i.net] Sent: Wednesday, November 18, 2009 3:14 AM To: freebsd-...@freebsd.org Cc: Guojun Jin; freebsd-stable@freebsd.org; questi...@freebsd.org Subject: Re: 8.0-RC3 USB lock up on mounting two partitions from one USB drive Hi, I'm not sure if this is an USB issue or not. If you get READ/WRITE errors and the drive simply dies then it might be the case. Else it is a system issue. There are quirks for mass storage which you can add to sys/dev/usb/storage/umass.c . --HPS On Wednesday 18 November 2009 08:33:07 Guojun Jin wrote: Did newfs on those partition and made things worsen -- restore completely fails: (I had experienced another similar problem on an IDE, which works well for 6.4 and 7.2, but 8.0.) This dirve works fine under FreeBSD 6.4. Is something new in 8.0 making disk partition schema changed? g_vfs_done():da0s3d[READ(offset=98304, length=16384)]error = 6 g_vfs_done():da0s3d[WRITE(offset=192806912, length=16384)]error = 6 fopen: Device not configured cannot create save file ./restoresymtable for symbol table abort? [yn] (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0xa, scs i status == 0x0 (da0:umass-sim0:0:0:0): removing device entry ugen1.2: DMI at usbus1 umass0: DMI Ultra HDD, class 0/0, rev 2.00/1.19, addr 2 on usbus1 umass0: SCSI over Bulk-Only; quirks = 0x umass0:0:0:-1: Attached to scbus0 da0 at umass-sim0 bus 0 target 0 lun 0 da0: DMI Ultra HDD 1.19 Fixed Direct Access SCSI-0 device da0: 40.000MB/s transfers da0: 114473MB (234441648 512 byte sectors: 255H 63S/T 14593C) Device da0s3d went missing before all of the data could be written to it; expect data loss. 99 23:19 sysinstall 100 23:20 newfs /dev/da0s3d 101 23:20 newfs /dev/da0s3e 102 23:21 mount /dev/da0s3d /mnt 103 23:21 cd /mnt 104 23:21 dump -0f - /home | restore -rf - 105 23:27 history 15 -Original Message- From: Guojun Jin Sent: Tue 11/17/2009 11:05 PM To: freebsd-stable@freebsd.org Cc: questi...@freebsd.org; freebsd-...@freebsd.org Subject: 8.0-RC3 USB lock up on mounting two partitions from one USB drive When mounting two partitions from a USB dirve, it can cause the drive access lock up for a long time. Details: Terminal 1 -- term1# mount /dev/da0s3d /mnt term1# cd /mnt ; rm -fr * when rm starts, go to terminal 2 and do: term2# mount /dev/da0s3e /dist ### this will hanging for a long time and USB hard drive activity light is off. After more than 1-2 minutes, mount returns, and the drive activity light is blinking, thus removing is going on. term2# ls /dist ### this will cause dUSB dirve hanging again -- no avtivity. Similarly, ls will finish in a couple of miniutes or longer, the rm command continues; but for a while, the drive activity will stop again. Reboot machine, repeat the above steps, and result will be the same. Reboot machine again, and just mount one partition, then doing rm -rf * without involve the second partition, rm will finish quickly. Has anyone obseved this behave on 8.0-RC? -Jin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
RE: 8.0-RC3 USB lock up on mounting two partitions from one USB drive
Did newfs on those partition and made things worsen -- restore completely fails: (I had experienced another similar problem on an IDE, which works well for 6.4 and 7.2, but 8.0.) This dirve works fine under FreeBSD 6.4. Is something new in 8.0 making disk partition schema changed? g_vfs_done():da0s3d[READ(offset=98304, length=16384)]error = 6 g_vfs_done():da0s3d[WRITE(offset=192806912, length=16384)]error = 6 fopen: Device not configured cannot create save file ./restoresymtable for symbol table abort? [yn] (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0xa, scs i status == 0x0 (da0:umass-sim0:0:0:0): removing device entry ugen1.2: DMI at usbus1 umass0: DMI Ultra HDD, class 0/0, rev 2.00/1.19, addr 2 on usbus1 umass0: SCSI over Bulk-Only; quirks = 0x umass0:0:0:-1: Attached to scbus0 da0 at umass-sim0 bus 0 target 0 lun 0 da0: DMI Ultra HDD 1.19 Fixed Direct Access SCSI-0 device da0: 40.000MB/s transfers da0: 114473MB (234441648 512 byte sectors: 255H 63S/T 14593C) Device da0s3d went missing before all of the data could be written to it; expect data loss. 99 23:19 sysinstall 100 23:20 newfs /dev/da0s3d 101 23:20 newfs /dev/da0s3e 102 23:21 mount /dev/da0s3d /mnt 103 23:21 cd /mnt 104 23:21 dump -0f - /home | restore -rf - 105 23:27 history 15 -Original Message- From: Guojun Jin Sent: Tue 11/17/2009 11:05 PM To: freebsd-stable@freebsd.org Cc: questi...@freebsd.org; freebsd-...@freebsd.org Subject: 8.0-RC3 USB lock up on mounting two partitions from one USB drive When mounting two partitions from a USB dirve, it can cause the drive access lock up for a long time. Details: Terminal 1 -- term1# mount /dev/da0s3d /mnt term1# cd /mnt ; rm -fr * when rm starts, go to terminal 2 and do: term2# mount /dev/da0s3e /dist ### this will hanging for a long time and USB hard drive activity light is off. After more than 1-2 minutes, mount returns, and the drive activity light is blinking, thus removing is going on. term2# ls /dist ### this will cause dUSB dirve hanging again -- no avtivity. Similarly, ls will finish in a couple of miniutes or longer, the rm command continues; but for a while, the drive activity will stop again. Reboot machine, repeat the above steps, and result will be the same. Reboot machine again, and just mount one partition, then doing rm -rf * without involve the second partition, rm will finish quickly. Has anyone obseved this behave on 8.0-RC? -Jin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
