after expanding filesystem, system reports correct filesize but only root can write
i open a new thread, since the problem migrated.
the old thread can be found here. it regards to the resizing activity. in short: i added some discs to a raid and expanded the filesystem with resize2fs. the system runs SLES 10. the system now reports the right size, but only root is able to write, all other users get a "no space left on device" message (or the like). the raid is formatted with ext3 , e2fsck reports no errors. for a short period of time (a few hours) after the expansion, everybody COULD write on that device, but at some point this changed. i am adding some information i can get: output of df -h Code:
/dev/mapper/raid2tb-raid2lv 16T 6,7T 8,7T 44% /raid2 Code:
Dateisystem INodes IUsed IFree %IUsed Code:
dumpe2fs 1.41.14 (22-Dec-2010) thank you very much! |
What does the command below do?
mount -o remount / When there is an error detected in the ext3 filesystem, it automatically goes read-only to protect the system. or: mount -o remount,rw / |
I didn't want to pull this thread off the zero replies list, but since you did manage to get a reboot done and you still have problems, I think you'd have to consider that f/s "suspect".
If it was me, I'd umount it, mkfs on it and restore. In fact I'd probably make it ext4 as the only time I use ext3 these days is for /boot. |
OK, we managed to mount a backup storage. now we want to retire the old /raid2 and set up a new filesystem on that.
but here it gets really weired: i wanted to unmount /raid2 and i am getting the notorious "device is busy" message. i tried any combination of lsof - fuser - /dev/mapper/raid2tb-raid2lv - /raid2 but couldn't get any output. I read that sometimes a running nfs-server is the culprit. but there is none running (i checked -- twice! ;) ) Anyway, i unmounted it with umount -l /raid2 yesterday . Today i tried to remount it, to do some checks before repartitioning and formatting but see this: Code:
mount /dev/mapper/raid2tb-raid2lv /raid2/ Code:
mount -o remount,r /raid2/ can i do something about this, e.g. finding out what process is accessing /raid2 (as i said lsof and fuser give me nothing) ? i am reluctant to restart the machine, as we had some serious troubles the last time we restarted it. |
Hmmm!
Quote:
Quote:
Quote:
|
Code:
mount -o remount,rw /raid2/ |
just to close this: restarted the system without mounting /dev/mapper/raid2tb-raid2lv . Tried to mount it, but it gave errors. I cannot remember specifics.
Anyway: Repartitioned, reformatted and remounted. |
All times are GMT -5. The time now is 01:59 AM. |