[Jfs-discussion] Filesystem went read-only after a resize
Brought to you by:
blaschke-oss,
shaggyk
From: Poul P. <pe...@ro...> - 2006-07-13 23:37:12
|
I've got a RedHat 9 box running the 2.4.32 kernel and jfsutils-1.0.17-6 (which is probably the ancient version that came with the OS). Using LVM, I recently added 10GB to a logical volume and then resized the JFS filesystem while it was online using the standard: mount -o remount,resize /my/path It resized fine, but within a short period of time (seconds to minutes) the file system switched to readonly and the only error in dmesg was: ERROR: (device lvm(58,6)): diFree: numfree > numinos I unmounted the filesystem and ran fsck.jfs: fsck.jfs version 1.0.17, 02-Apr-2002 The current device is: /dev/vg01/p4port_1666 Block size in bytes: 4096 File system size in blocks: 18350080 Phase 0 - Replay Journal Log Phase 1 - Check Blocks, Files/Directories, and Directory Entries. Phase 2 - Count Links. Phase 3 - Rescan for Duplicate Blocks and Verify Directory Tree. Phase 4 - Report Problems. Phase 5 - Check Connectivity. Phase 6 - Perform Approved Corrections. Phase 7 - Rebuild File/Directory Allocation Maps. Phase 8 - Rebuild Disk Allocation Maps. File system is clean. After which, it mounted and appears to be fine.=20 We use JFS on a lot of our production systems and this is the only one to every experience this problem on a resize. Of course, most of our other systems are all running kernel 2.6 variants and more recent JFS tools. Was this a fluke? Any idea what might have caused it to fail? Thanks, -poul |