LinuxQuestions.org - after expanding filesystem, system reports correct filesize but only root can write

- Linux - General (https://www.linuxquestions.org/questions/linux-general-1/)

- - after expanding filesystem, system reports correct filesize but only root can write (https://www.linuxquestions.org/questions/linux-general-1/after-expanding-filesystem-system-reports-correct-filesize-but-only-root-can-write-917182/)

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

output of df -i

Code:

Dateisystem                  INodes    IUsed  IFree      %IUsed 

/dev/mapper/raid2tb-raid2lv  2097152000  351420 2096800580 1%    /raid2

output of dumpe2fs -h

Code:

dumpe2fs 1.41.14 (22-Dec-2010)

Filesystem volume name:  <none>

Last mounted on:          <not available>

Filesystem UUID:          XXXXXXXXXXXXXXXXXXXXXXXXXX

Filesystem magic number:  0xEF53

Filesystem revision #:    1 (dynamic)

Filesystem features:      has_journal resize_inode filetype needs_recovery sparse_super large_file

Default mount options:    (none)

Filesystem state:        clean

Errors behavior:          Continue

Filesystem OS type:      Linux

Inode count:              2097152000

Block count:              4194304000

Reserved block count:    25246337

Free blocks:              2337720331

Free inodes:              2096800474

First block:              0

Block size:              4096

Fragment size:            4096

Reserved GDT blocks:      24

Blocks per group:        32768

Fragments per group:      32768

Inodes per group:        16384

Inode blocks per group:  512

Filesystem created:      Wed Jan 12 12:40:41 2011

Last mount time:          Mon Dec  5 07:12:56 2011

Last write time:          Mon Dec  5 07:12:56 2011

Mount count:              1

Maximum mount count:      24

Last checked:            Mon Dec  5 01:24:41 2011

Check interval:          15552000 (6 months)

Next check after:        Sat Jun  2 02:24:41 2012

Reserved blocks uid:      0 (user root)

Reserved blocks gid:      0 (group root)

First inode:              11

Inode size:              128

Journal inode:            8

Default directory hash:  tea

Directory Hash Seed:      XXXXXXXXXXXXXXXXXXXXXXXXX

Journal backup:          inode blocks

Jounal properties:        journal_incompat_revoke

Journal size:            128M

Journal length:            32768

Journal sequence:          0x0042b6f5

Journal start:            23175

i am slowly running out of ideas... :( everything looks ok, but i cannot write on that thing.

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/

mount: /dev/mapper/raid2tb-raid2lv already mounted or /raid2/ busy

and

Code:

mount -o remount,r /raid2/

mount: /raid2 not mounted already, or bad option

which is quite contradictory.

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:

or bad option

Quote:

mount -o remount,r

Or good option:

Quote:

mount -o remount,rw /raid2/

Code:

mount -o remount,rw /raid2/

mount: /raid2 not mounted already, or bad option

had not bet on that, though.

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.