[lkml]   [2000]   [Dec]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectIDE fs corruption in 2.4.0-test11?
My system running 2.4.0-test11 recently trashed itself and I was
wondering what steps I should take to ensure UDMA is running OK
and not trashing itself.

Are there options in hdparm that could conflict with 2.4's handling
of UDMA that would cause all writable partitions on the drive to
self-destruct? This is what happened to me last weekend except for
/usr, which was mounted read-only at the time.

2.4.0-test11 spontaneously just rebooted itself for no reason,
so I decided booting into 2.2.17 would be a good idea to check
to make sure everything was fine. 2.2.17 fsck'd all the partitions
and was happy and went on.

I then rebooted back into 2.4.0-test11 (or tried to) and LILO greeted
me with a lovely "LIL-".

I booted from rescue disks and attempted to fsck the partitions.
I had to specify the superblock and eventually got a huge string of
"Illegal blocks in inodes". After fscking "/", I noticed /etc was
gone. Same thing happened in /var and /home with basically no
data being fixed or recovered. I had to reformat everything.

Which options in hdparm are considered dangerous to use in 2.4?
I had 32-bit I/O set (-c 1) , DMA set on (-d 1), multiple sector I/O
(-m 16). The drive in question is a 45 gigabyte Western Digital Caviar

I heard the multiple sector I/O may be bad for the drives.. is this

Thanks in advance,


ps. Please reply directly to my e-mail address as I am not
subscribed to linux-kernel.

Do You Yahoo!?
Yahoo! Shopping - Thousands of Stores. Millions of Products.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 12:51    [W:0.023 / U:0.164 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site