Date: Wed, 20 Jun 2001 23:21:23 -0700 From: Bakul Shah <bakul@bitblocks.com> To: freebsd-fs@freebsd.org Subject: Strange scsi disk behavior on a freebsd system Message-ID: <200106210621.CAA14821@glatton.cnchost.com>
next in thread | raw e-mail | index | archive | help
Readonly mount of the disk allows me to access files on it fine but fsck fails with messages like ** /dev/da0a ** Last Mounted on /u ** Phase 1 - Check Blocks and Sizes UNKNOWN FILE TYPE I=6 CLEAR? [yn] n UNKNOWN FILE TYPE I=15 CLEAR? [yn] n UNKNOWN FILE TYPE I=38 CLEAR? [yn] n UNKNOWN FILE TYPE I=47 CLEAR? [yn] n UNKNOWN FILE TYPE I=56 CLEAR? [yn] n UNKNOWN FILE TYPE I=70 CLEAR? [yn] n UNKNOWN FILE TYPE I=79 CLEAR? [yn] This goes on an on. I also see messages like PARTIALLY ALLOCATED INODE I=4149 CLEAR? [yn] n ls -l on the file with inode=6 reveals nothing funny. catting the file shows nothing abnormal. `dd </dev/da0a >/dev/null bs=1m' works fine. `camcontrol defects da0 -f bfi' fails with an error: camcontrol: Error returned from read defect data command The disk has two partitions and both have the same problem. So finally I newfsed one of the two partitions and even on a freshly newfsed partition I get the same sort of errors. Why would readonly mount, ls, cat and dd work but fsck fail? The same behavior has been observed for the past 6+ months (after the disk was moved long distance) on various freebsd-current kernels. This is an old <QUANTUM XP34550S LXY4> 4Gig drive. The disk data is already saved and I do intend to throw the disk away but this behavior puzzles me. This behavior seems disk related not s/w related but why would only fsck complain? Any guesses anyone? Thanks for any insight. -- bakul To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200106210621.CAA14821>