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
/dev/mapper/raid2tb-raid2lv 16T 6,7T 8,7T 44% /raid2
output of df -i
Dateisystem INodes IUsed IFree %IUsed
/dev/mapper/raid2tb-raid2lv 2097152000 351420 2096800580 1% /raid2
output of dumpe2fs -h
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!