Theodore Tso a écrit :
On Fri, Sep 18, 2009 at 01:24:32PM -0500, Eric Sandeen wrote:
Delalloc should be mostly ok in that kernel, but quota doesn't handle
it. So dropping quota -or- dropping delalloc should suffice.
OTOH, the -o nodelalloc paths have not gotten a lot of test coverage, so
caveats apply.
I haven't dont a -o delalloc test in a while, but at one point,
probably about 2-3 months ago, I did do a regression test run using
the xfsqa test suite with -o delalloc. Of course, just because
mainline -o delalloc has been tested doesn't say that much about RHEL
5.4's -o delalloc --- there's a reason why it was labelled a
Technology Preview on RHEL 5.4. :-)
- Ted
I would love to test that option (-o nodelalloc) instead of move back to
ext3.
however I don't understand what it is ... Am I taking risk in term of
integrity of data if I set it ?, or just losing performances ?
anyway, I'am not sure it is available, when I search it in "man mount",
I can't find it, is it an undocumennted option ?
...
well it appears to be available as I set it on a test partition with
success apparently
$ mount
/dev/mapper/VolGroup03S2IA-LogVolS2ia01 on /disk00 type ext4dev
(rw,_netdev,acl,usrquota,grpquota,nodelalloc)
but now, how can I check that there's no more pb on that specific
partition( /disk00)?
when kernel complains this way for example:
Sep 16 18:06:45 gizeh kernel: mpage_da_map_blocks block allocation
failed for inode 39419 at logical offset 0 with max blocks 2 with error
-122
Sep 16 18:06:45 gizeh kernel: This should not happen.!! Data will be lost
I've no indication from which partition that inode is. there's so many
error message like this that is won't be easy to tell that none comes
from /disk00 .
thanks for your help .
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
