Ok, so my system has been up and running pretty good for the past few weeks, but I recently ran into a small problem. Lets say for example that I extract a DVD to a folder on my 250GB hard drive (/storage/WD250) from a windows machine using the admin account I have setup known as ktriggs. I do have disk quotas enabled but nothing setup for this specific user. Once I delete this .img file that is the DVD the filesystem automatically become read-only for some reason even though that's not what it is setup to be. See below:

[root@haze ~]# ls -ls /storage/WD250
total 172
12 -rw------- 1 root root 8192 Feb 22 06:40 aquota.user
12 -rw------- 1 root root 7168 Feb 14 01:40 aquota.user.new
84 -rwxr--r-- 1 ktriggs root 75966 Mar 3 07:22 bookmarks.html
8 drwxr-xr-x 5 ktriggs root 4096 Mar 1 07:02 DVDs
16 drwx------ 2 root root 16384 Feb 7 18:27 lost+found
16 drwxr-xr-x 236 root root 12288 Dec 31 1969 Music

this is what I get when I try to reset the permissions I want assigned:

[root@haze ~]# chmod 775 /storage/WD250
chmod: changing permissions of `/storage/WD250': Read-only file system

Then, when I reboot the server everything goes back to normal until I delete another file. Any help?

the kernel may be seeing IO errors to the device and remounting read only to protect the data from corruption. does anything show up in dmesg when this happens? you might well want to manually run fsck against this partition to check for file system inconsistencies.

This is what the output is when I run "fsck /dev/sda":

[root@haze ~]# fsck /dev/sdb
fsck 1.38 (30-Jun-2005)
e2fsck 1.38 (30-Jun-2005)
Group descriptors look bad... trying backup blocks...
fsck.ext2: Bad magic number in super-block while trying to open /dev/sdb

The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>

then I run the command it tells me to and I get this:

[root@haze ~]# e2fsck -b 8193 /dev/sdb
e2fsck 1.38 (30-Jun-2005)
e2fsck: Bad magic number in super-block while trying to open /dev/sdb

The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>

I read through the dmesg output and found a few lines that looked useful, but I'm no sure:

sd 3:0:0:0: Attached scsi disk sdb
EXT3-fs: INFO: recovery required on readonly filesystem.
EXT3-fs: write access will be enabled during recovery.


Thanks so much acid_kewpie

you run fsck against a partition, /dev/sda1 not a device, /dev/sda

this is what I get:

[root@haze ~]# fsck /dev/sdb1
fsck 1.38 (30-Jun-2005)
e2fsck 1.38 (30-Jun-2005)
/storage/WD250: clean, 50848/60948480 files, 34384240/60918472 blocks
[root@haze ~]#