From: Stan Hoeppner <stan@hardwarefreak.com>
To: daobang wang <wangdb1981@gmail.com>
Cc: "Mathias Burén" <mathias.buren@gmail.com>,
linux-raid <linux-raid@vger.kernel.org>
Subject: Re: RAID5 created by 8 disks works with xfs
Date: Sun, 01 Apr 2012 00:13:20 -0500 [thread overview]
Message-ID: <4F77E3F0.2030802@hardwarefreak.com> (raw)
In-Reply-To: <CACwgYDNitxymtLT3SMw6m0_utqAzXPsOT5Y1CpwrjW1fN+xuqA@mail.gmail.com>
On 3/31/2012 9:05 PM, daobang wang wrote:
> There is another problem occurred, it seems that the file system was
> damaged when the pressure is very high,
What kernel version are you using? Did you get an oops? What's in dmesg?
> it reported input/output error
Actual errors would be very helpful.
> when i typed ls or other command, and I tried to repair it with
> xfs_repair /dev/vg00/lv0000, the xfs_repir alloc memory failed, we
Did XFS automatically unmount the filesystem? If not, the error
reported may not indicate a problem with the filesystem. XFS shuts
filesystems down when it encounters serious problems.
> have 4GB memory on the machine, and the logical volume was a little
> more than 15TB, Could it be repair successfully if we have enough
> memory?
Hard to say. Depends on what happened and the extent of the damage, if
any. You've presented no log or debug information. I would think 4GB
should be plenty to run xfs_repair. Try
$ xfs_repair -n -vv -m 1 /dev/vg00/lv0000
dmem = in the output tells you how much RAM is needed for xfs_repair.
If it's more than 2GB and you're using a PAE kernel, switch to a 64 bit
kernel and 64 bit userland. If dmem is over 4GB then you need more
DIMMs in the machine. Or maybe simply dropping caches before running
xfs_repair might help:
$ echo 3 > /proc/sys/vm/drop_caches
--
Stan
next prev parent reply other threads:[~2012-04-01 5:13 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-31 1:22 RAID5 created by 8 disks works with xfs daobang wang
2012-03-31 7:59 ` Mathias Burén
2012-03-31 20:09 ` Stan Hoeppner
2012-04-01 1:16 ` daobang wang
2012-04-01 2:05 ` daobang wang
2012-04-01 5:13 ` Stan Hoeppner [this message]
2012-04-01 3:51 ` Stan Hoeppner
2012-04-01 5:12 ` daobang wang
2012-04-01 5:40 ` Stan Hoeppner
2012-04-01 5:59 ` daobang wang
2012-04-01 6:20 ` daobang wang
2012-04-01 7:08 ` Marcus Sorensen
2012-04-02 3:47 ` Stan Hoeppner
2012-04-05 0:48 ` daobang wang
[not found] ` <CACwgYDOtCoVF-p+KKqPYxHhA4vWF78Ueecx9hcVWLoyxFWzV9Q@mail.gmail.com>
2012-04-05 21:01 ` Stan Hoeppner
2012-04-06 0:25 ` daobang wang
2012-04-06 2:33 ` daobang wang
2012-04-06 6:00 ` Jack Wang
2012-04-06 6:45 ` daobang wang
2012-04-06 6:49 ` daobang wang
2012-04-06 8:18 ` Stan Hoeppner
2012-04-06 8:45 ` daobang wang
2012-04-06 11:12 ` Stan Hoeppner
2012-04-18 2:23 ` daobang wang
2012-04-02 3:12 ` Stan Hoeppner
2012-04-01 10:33 ` David Brown
2012-04-01 12:28 ` John Robinson
2012-04-02 6:59 ` David Brown
[not found] ` <CA+res+QkLi7sxZrD-XOcbR47CeJ5gADf7P6pa1w1oMf8CKSB4g@mail.gmail.com>
2012-04-02 8:01 ` John Robinson
2012-04-02 10:01 ` Jack Wang
2012-04-02 10:28 ` John Robinson
2012-04-02 20:41 ` Stan Hoeppner
2012-04-02 5:43 ` Stan Hoeppner
2012-04-02 7:04 ` David Brown
2012-04-02 20:21 ` Stan Hoeppner
2012-04-01 4:52 ` Stan Hoeppner
2012-04-01 8:06 ` John Robinson
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=4F77E3F0.2030802@hardwarefreak.com \
--to=stan@hardwarefreak.com \
--cc=linux-raid@vger.kernel.org \
--cc=mathias.buren@gmail.com \
--cc=wangdb1981@gmail.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;
as well as URLs for NNTP newsgroup(s).