From: tirumalareddy marri <tirumalareddymarri@yahoo.com>
To: sandeen@sandeen.net
Cc: linux-raid@vger.kernel.org, linux-ext4@vger.kernel.org
Subject: Re: 64k Page size + ext3 errors
Date: Mon, 28 Jul 2008 16:29:23 -0700 (PDT) [thread overview]
Message-ID: <590218.14781.qm@web81301.mail.mud.yahoo.com> (raw)
Hi Eric,
This is PowerPC architecture from AMCC(I work for AMCC). I am using 2.6.25 Kernel. According your suggestion I tested with out RAID I did not see any EXT-3 errors. I use "sum" command to check the data integrity of the files.
I ported ADMA driver to do HW accelerated XOR calculations . Also please note that RAID-5 works with 4K Page size.
Thanks,
Marri
----- Original Message ----
From: "sandeen@sandeen.net" <sandeen@sandeen.net>
To: tirumalareddy marri <tirumalareddymarri@yahoo.com>
Cc: linux-raid@vger.kernel.org; linux-ext4@vger.kernel.org
Sent: Sunday, July 27, 2008 6:52:05 PM
Subject: Re: 64k Page size + ext3 errors
> I am using HW accelerated XOR engine for RAID-5 . I am seeing EXT3-fs
> errors when I use 64K page size. When I use 4K page size I don't see any
> issue. As many of you know, we will get better performance when we store
> bigger files like videos.
Do you think it is specific to the filesystem on raid-5? Have you tested
w/o md? I'd be a little surprised if the problem is at the raid layer (so
cc'ing the ext3/4 list), but maybe you tested that already.
Which arch is it, and which kernel? How big is the filesystem? With full
geometry information it might be easier for someone to reproduce & debug.
Thanks,
-Eric
> When I copy 128MB size files using 64k page size no issues seen. When I
> tried to copy 1.8 GB file with 64KB page size support I am seeing the
> following errors. Any clue what could be wrong.
>
> Errors 1:
> EXT3-fs error (device md0): ext3_new_block: Allocating block in system
> zone - blocks from 65533, length 1
> EXT3-fs error (device md0): ext3_new_block: Allocating block in system
> zone - blocks from 65534, length 1
>
>
> Errors2:
> EXT3-fs error (device md0): ext3_readdir: bad entry in directory #2:
> rec_len % 4 != 0 - offset=0, inode=3040
>
>
> Thanks in Advance,
> Marri
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2008-07-28 23:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-28 23:29 tirumalareddy marri [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-07-28 23:44 64k Page size + ext3 errors tirumalareddy marri
2008-07-28 23:42 tirumalareddy marri
2008-07-29 0:33 ` Roger Heflin
2008-07-27 23:28 tirumalareddy marri
2008-07-28 1:52 ` sandeen
2008-07-28 8:04 ` Dan Williams
2008-07-28 2:10 ` Roger Heflin
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=590218.14781.qm@web81301.mail.mud.yahoo.com \
--to=tirumalareddymarri@yahoo.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=sandeen@sandeen.net \
/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).