[Wylug-help] Strange disk problems

[DavidPashleyDavid@davidpashley.com]

I have a strange problem. I have a large drive as hda (30Gb). I can not
write to hda7. Below is the output of 'p' in fdisk

Disk /dev/had: 255 heads, 63 sectors, 3737 cylinders
Units = cylinders of 16065 * 512 bytes

   Device Boot    Start       End    Blocks   Id  System
   /dev/hda1   *         1         3     24066   83  Linux
   /dev/hda2             4      1308  10482412+   6  FAT16
   /dev/hda3          1309      1690   3068415    c  Win95 FAT32 (LBA)
   /dev/hda4          1691      3737  16442527+   5  Extended
   /dev/hda5          1691      1721    248976   82  Linux swap
   /dev/hda6          1722      1783    497983+  83  Linux
   /dev/hda7          1784      2756   7815591   83  Linux
   /dev/hda8          2757      3005   2000061   83  Linux
   /dev/hda9          3006      3129    995998+  83  Linux
   /dev/hda10         3130      3737   4883728+  83  Linux

/dev/hda7 is /usr and any attempt to creae a file on the drive under
2.4.0-test5 and 2.4.0-test7-pre6 results in "Input/output Error". Under
2.2.15 I get "No space left on device". df -h reports the following

Filesystem            Size  Used Avail Use% Mounted on
/dev/hda6             471M  317M  129M  71% /
/dev/hda1              23M  9.4M   12M  42% /boot
/dev/hda7             7.4G  4.6G  2.4G  65% /usr
/dev/hda8             1.9G  895M  953M  49% /var
/dev/hda10            4.6G  1.4G  3.0G  31% /home
/dev/hda9             969M  884k  919M   1% /tmp
/dev/hda3             2.9G  1.9G  1.0G  65% /shared
shm                   8.0G  1.3M  7.9G   1% /var/shm

If I take a file that already exists on the drive and perform `rm file;
touch file` I get no error. Performing a `sync` before the `touch`
doesn't make a difference. I have not tried a `umount ; mount` but I'll
try it next time I'm in single user.

I've tried running fsck and badblocks, but doesn't seem to work. Is
there a way to remove which blocks are marked as bad and recheck eash
block from scratch. I'm surprised it only affects the on partition as it
isn't the last partition on the drive and later partitions work find.

Any ideas would be fantastic.

BTW
Linux David 2.4.0-test7 #3 SMP Sat Aug 19 01:26:23 BST 2000 i686 unknown
running debian woody 2.3
-- 
David Pashley
david@davidpashley.com
[This line is still unavailable]