From: Jimmy Dorff <jdorff@phy.duke.edu>
To: xfs@oss.sgi.com
Subject: problems with xfs_growfs after lvextend
Date: Wed, 23 Sep 2009 17:04:22 -0400 [thread overview]
Message-ID: <4ABA8D56.2040101@phy.duke.edu> (raw)
Hello,
I'm having a problem with a corrupt xfs filesystem after attempting to
grow the filesystem.
The problem is very similar to this post:
http://www.redhat.com/archives/linux-lvm/2005-November/msg00026.html
Except that xfs_repair never finds a secondary superblock.
Details:
CentOS Linux,
kernel 2.6.18-128.1.16.el5.centos.plus x86_64
lvm2-2.02.40-6.el5
originally: xfsprogs-2.9.4-1.el5.centos.x86_64
This sever has been up and running for a few months w/o problems. Today
we added some disks to a 3ware controller. The disks were all tested
individually before installation.
Used "tw_cli" to configure a new RAID volume, which appeared in Linux as
normal (/dev/sdd).
# pvcreate /dev/sdd
# vgextend array_vg /dev/sdd
# lvextend /dev/array_vg/data --size +12T
This all worked w/o any errors. vgdisplay and lvdisplay all report the
correct info and sizes.
The 6TB xfs filesystem on /dev/array_vg/data was mounted as "/srv/data"
# xfs_growfs /srv/data
The size of the filesystem didn't change. I unmounted it and tried
again, but no change. However, now I can't mount the filesystem at all.
xfs_check causes xfs_db to use so much memory as to hang up the system.
xfs_repair reports:
Phase 1 - find and verify superblock...
superblock read failed, offset 19791209299968, size 2048, ag 96, rval 0
fatal error -- Invalid argument
Also, I've noticed this in syslog:
kernel: attempt to access beyond end of device
kernel: dm-1: rw=0, want=64424509440, limit=38654705664
kernel: I/O error in filesystem ("dm-1") meta-data dev dm-1 block
0xeffffffff ("xfs_read_buf") error 5 buf count 512
kernel: XFS: size check 2 failed
I've trying using xfs_repair from xfsprogs 3.0.3, but it made no
difference.
Any suggestions ? Any help understanding why this didn't work ?
Thanks,
Jimmy Dorff
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2009-09-23 21:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-23 21:04 Jimmy Dorff [this message]
2009-09-23 21:12 ` problems with xfs_growfs after lvextend Eric Sandeen
2009-09-23 21:37 ` Russell Cattelan
2009-09-23 23:21 ` Jimmy Dorff
2009-09-24 0:00 ` Russell Cattelan
2009-09-24 0:54 ` Jimmy Dorff
2009-09-23 21:47 ` Michael Monnerie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4ABA8D56.2040101@phy.duke.edu \
--to=jdorff@phy.duke.edu \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox