Failing to remove corrupted files after RAID resize

scott12087 · 03-20-2011, 08:31 PM

I am running a RAID 6 setup on Debian with 4 drives. I recently shrunk the size of the RAID partitions by failing one drive in the array, shrinking the partition, then adding it back to the array and allowing it to rebuild. Did this for each of the partitions and then used mdadm grow to resize the array to the max size of the new partitions. I found this in a guide somewhere but I'm unable to find where I read about it now. I will post it later if I find.

Anyway, this corrupted some files and directories on the disk. They're not critical, just some media files. I'm trying to remove the corrupted files and keep getting the message:

Code:

rm: cannot remove filename: Operation not permitted

It does this even if I use sudo or -f. I've obviously corrupted something on the drive, but I don't know where to go from here. I've been digging through old forums but I haven't been able to find much. If anybody out there could point me in the right direction for solving this problem that would be great! Thanks!

tva · 03-21-2011, 07:52 AM

Not sure if it does any good but have you tried fsck?

scott12087 · 03-23-2011, 07:12 PM

Not much to see from fsck. Maybe I'm not doing it right?

Code:

fsck /dev/md0
fsck from util-linux-ng 2.17.2
e2fsck 1.41.12 (17-May-2010)
fsck.ext3: No such file or directory while trying to open /dev/md0

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>

Code:

sudo fsck /dev/sda
fsck from util-linux-ng 2.17.2
e2fsck 1.41.12 (17-May-2010)
fsck.ext2: Device or resource busy while trying to open /dev/sda
Filesystem mounted or opened exclusively by another program?

The device or resource busy message shows up for each of the individual drives (sda-sdd). Not sure why.

tva · 03-24-2011, 03:16 AM

Did you try fsck with filesystem mounted or unmounted? IIRC it should be unmounted. Anyways, I'm not sure at all if it helps with your problem, not very experienced myself with disk problems..