From: Vitaly Fertman <vitaly@namesys.com>
To: Michael Weissenbacher <webmaster@dermichi.com>,
ReiserFS List <reiserfs-list@namesys.com>
Subject: Re: "wrong bytes" with files >=4GiB
Date: Thu, 16 Sep 2004 20:08:57 +0400 [thread overview]
Message-ID: <200409162008.57769.vitaly@namesys.com> (raw)
In-Reply-To: <413C5521.6080700@dermichi.com>
On Monday 06 September 2004 16:16, Michael Weissenbacher wrote:
> I'm using kernel 2.6.9-rc1-mm1 (patched for the page-size bug) and
> reiser4progs1.0.0. I am able to reproduce a "wrong bytes" problem by
> doing the following:
> # dd if=/dev/urandom bs=4096 count=1048576 of=/mnt/tmp/testfile
> # umount /mnt/tmp
> # fsck.reiser4 /dev/sda1
> ...
> FSCK: Node (45223670), item (3), [2a:7465737466696c:1000f] (stat40):
> wrong bytes(4294967296), Should be (0).
> ...
> 1 fixable corruptions were detected in the FileSystem. Run with --fix
> option to fix them.
>
> When doing a fsck.reiser4 with --fix parameter it says
> FSCK: Node (45223670), item (3), [2a:7465737466696c:1000f] (stat40):
> wrong bytes
> (4294967296), Fixed to (0).
>
> and after that it says that the fs is consistent. I cannot find any
> difference in the file on the filesystem though.
> Is this actually harmful or is it just "statistic" data?
the only problem here is that bytes field becomes wrong.
this does not corrupt data.
> If i'm doing the same test with count=1048575 no corruption is reported
> and if i'm doing it for files >4GiB i always get the problem (with
> different numbers of course).
> I can sent the full fsck output if needed.
> BTW this problem also occurs with kernel 2.6.8.1-mm2.
I have found it, thank you for hitting the bug, fixed.
--
Thanks,
Vitaly Fertman
prev parent reply other threads:[~2004-09-16 16:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-06 12:16 "wrong bytes" with files >=4GiB Michael Weissenbacher
2004-09-06 15:03 ` Vladimir Saveliev
2004-09-16 16:08 ` Vitaly Fertman [this message]
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=200409162008.57769.vitaly@namesys.com \
--to=vitaly@namesys.com \
--cc=reiserfs-list@namesys.com \
--cc=webmaster@dermichi.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.