I did this:
lvextend -L+8T /dev/lvmsas/media
Extending logical volume media to 32.50 TiB
Logical volume media successfully resized
And then this:
mount -o remount,resize /mnt/media
which unfortunately failed with the error:
mount: /dev/lvmsas/media: can't read superblock
Now when I run fsck it says:
fsck.jfs version 1.1.15, 04-Mar-2011
processing started: 11/10/2013 0:19:46
Using default parameter: -p [xchkdsk.c:3033]
The current device is: /dev/lvmsas/media [xchkdsk.c:1527]
Open(...READ/WRITE EXCLUSIVE...) returned rc = 0 [fsckpfs.c:3233]
Primary superblock is valid. [fsckmeta.c:1551]
The type of file system for the device is JFS. [xchkdsk.c:1544]
Block size in bytes: 4096 [xchkdsk.c:1857]
Filesystem size in blocks: 6576668672 [xchkdsk.c:1864]
**Phase 0 - Replay Journal Log [xchkdsk.c:1871]
LOGREDO: Log superblock contains invalid magic number. [logredo.c:529]
logredo failed (rc=-268). fsck continuing. [xchkdsk.c:1901]
**Phase 1 - Check Blocks, Files/Directories, and Directory Entries
[xchkdsk.c:1996]
Primary metadata inode A2 is corrupt. [fsckmeta.c:3171]
Duplicate reference to 131199 block(s) beginning at offset 16 found in file
system object MA2. [fsckwsp.c:452]
Inode A2 has references to cross linked blocks. [fsckwsp.c:1772]
Duplicate reference to 8243 block(s) beginning at offset 1073700813 found in
file system object MA2. [fsckwsp.c:452]
Inode A2 has references to cross linked blocks. [fsckwsp.c:1772]
Duplicate reference to 24556 block(s) beginning at offset 1073709056 found in
file system object MA2. [fsckwsp.c:452]
Inode A2 has references to cross linked blocks. [fsckwsp.c:1772]
Duplicate reference to 8243 block(s) beginning at offset 1342128077 found in
file system object MA2. [fsckwsp.c:452]
Inode A2 has references to cross linked blocks. [fsckwsp.c:1772]
Duplicate reference to 122953 block(s) beginning at offset 1342136320 found in
file system object MA2. [fsckwsp.c:452]
Inode A2 has references to cross linked blocks. [fsckwsp.c:1772]
Duplicate reference to 8243 block(s) beginning at offset 2415837133 found in
file system object MA2. [fsckwsp.c:452]
Inode A2 has references to cross linked blocks. [fsckwsp.c:1772]
Duplicate reference to 172152 block(s) beginning at offset 2415845376 found in
file system object MA2. [fsckwsp.c:452]
Inode A2 has references to cross linked blocks. [fsckwsp.c:1772]
Duplicate reference to 12339 block(s) beginning at offset 3892187085 found in
file system object MA2. [fsckwsp.c:452]
Inode A2 has references to cross linked blocks. [fsckwsp.c:1772]
Duplicate reference to 315651 block(s) beginning at offset 3892199424 found in
file system object MA2. [fsckwsp.c:452]
Inode A2 has references to cross linked blocks. [fsckwsp.c:1772]
Errors detected in the Primary File/Directory Allocation Table.
[fsckmeta.c:1890]
Errors detected in the Secondary File/Directory Allocation Table.
[fsckmeta.c:1895]
CANNOT CONTINUE. [fsckmeta.c:1902]
processing terminated: 11/10/2013 0:19:46 with return code: -10049 exit
code: 4. [xchkdsk.c:475]
I'm guessing the filesystem is not significantly damaged, but rather that
fsck.jfs doesn't know how to rollback a failed resize operation. I can mount
the filesystem read-only without issue and everything appears to be intact and
working correctly in that mode.
I crossed 32 TB with the underlying LVM expansion and I fear I may have hit
this problem:
http://sourceforge.net/p/jfs/bugs/277/
but I couldn't find anything that looks like confirmation of those reports or a
fix/workaround.
If I had enough space I'd all copy off this filesystem and restore to a fresh
one, but I don't have 24 TB to spare at the moment. So I'd like to get the
existing filesystem writable if at all possible. Resized would be nice too, but
that's an easier issue to work around. Any suggestions to that end would be
appreciated.
Zach
smime.p7s
Description: S/MIME cryptographic signature
------------------------------------------------------------------------------ November Webinars for C, C++, Fortran Developers Accelerate application performance with scalable programming models. Explore techniques for threading, error checking, porting, and tuning. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
_______________________________________________ Jfs-discussion mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jfs-discussion
