From: Tao Ma <tm@tao.ma>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] useless tools - tunefs.ocfs2,fsck.ocfs2
Date: Thu, 20 Jan 2011 21:59:47 +0800 [thread overview]
Message-ID: <4D383FD3.7000602@tao.ma> (raw)
In-Reply-To: <4D383BDC.4050400@mp.pl>
On 01/20/2011 09:42 PM, Pawel wrote:
> One of ocfs2 filesystem has some errors.
> 1. fsck.ocfs2 informs me that : "I/O error on channel while reading
> .. " It was NOT TRUE - I was able to read and write entire storage over
> the network multiple times.
It means it meet I/O error in some ocfs2 disk structure, not the disk.
> 2. becouse of CRC errors and suggestion to disable metaecc I run
> tunefs.ocfs2 --fs-features=nometaecc /dev/xxx
> funefs allocate 9,89 GB of virtual memory and 95% of phisical memory
> (4GB). After 4 hours process has been killed - because of out of memory.
>
> I have to recreate new filesystem and restore data from backup.
>
> I try to use tools in version 1.4 and 1.6 (newest)
> Filesystem is quite small 250GB and less than 10 000 files, exported by aoe.
> Additionally on the new clean FS - running tunefs.ocfs2
> --fs-features=nosparse behave in the same way
I knew a similar bug in fsck.ocfs2, but didn't meet any similar issue in
tunefs.ocfs2.
The bug in fsck is fixed by b987ee2 "fsck.ocfs2: Only ask available
pages in o2fsck_init_cache."
A new clean FS will cause so much memory, strange?
would you mind run o2image and give us the image?
Then I can test it locally.
anyway, thanks for the test.
Regards,
Tao
next prev parent reply other threads:[~2011-01-20 13:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-20 13:42 [Ocfs2-devel] useless tools - tunefs.ocfs2,fsck.ocfs2 Pawel
2011-01-20 13:59 ` Tao Ma [this message]
2011-01-20 19:30 ` Sunil Mushran
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=4D383FD3.7000602@tao.ma \
--to=tm@tao.ma \
--cc=ocfs2-devel@oss.oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.