From: "Marco Berizzi" <pupilla@hotmail.com>
To: "Nikita Danilov" <Nikita@Namesys.COM>
Cc: <linux-kernel@vger.kernel.org>,
"Reiserfs mail-list" <Reiserfs-List@Namesys.COM>
Subject: Re: ReiserFS corruption with samba 3.0.2a
Date: Wed, 18 Feb 2004 15:08:19 +0100 [thread overview]
Message-ID: <Sea2-DAV57V87PdIv650000b53f@hotmail.com> (raw)
In-Reply-To: 16435.27477.679757.404161@laputa.namesys.com
Nikita Danilov wrote:
> Marco Berizzi writes:
> > Hello.
> >
> > I'm experimenting this problem with samba 3.0.2a and linux 2.4.24
> > with ReiserFS. When I copy (put) a large file (5GB) from a Windows NT
> > terminal server edition sp6a machine to the samba-linux box I get this
> > error:
> >
> > Feb 17 18:01:11 Mimas kernel: ide0(3,8):vs-4080: reiserfs_free_block: free_block (0308:4999052)[dev:blocknr]: bit already cleared
> > Feb 17 18:01:11 Mimas kernel: ide0(3,8):vs-4080: reiserfs_free_block: free_block (0308:4997935)[dev:blocknr]: bit already cleared
> > Feb 17 18:02:48 Mimas kernel: ide0(3,8):vs-4080: reiserfs_free_block: free_block (0308:902445)[dev:blocknr]: bit already cleared
> > Feb 17 18:02:48 Mimas kernel: ide0(3,8):vs-4080: reiserfs_free_block: free_block (0308:902286)[dev:blocknr]: bit already cleared
> >
>
> Are there any other error messages before these?
No, no errors before these.
> > Samba 2.2.8a doesn't show this behaviour.
> >
> > The linux box is Slackware 9.1 (gcc 3.2.3 linux 2.4.24 glibc 2.3.2).
> > It's easy for me to reproduce the problem.
> >
> > Hints?
>
> Did target file exist before copy?
No. The directory was clean.
prev parent reply other threads:[~2004-02-18 14:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-18 11:03 ReiserFS corruption with samba 3.0.2a Marco Berizzi
2004-02-18 13:40 ` Nikita Danilov
2004-02-18 14:08 ` Marco Berizzi [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=Sea2-DAV57V87PdIv650000b53f@hotmail.com \
--to=pupilla@hotmail.com \
--cc=Nikita@Namesys.COM \
--cc=Reiserfs-List@Namesys.COM \
--cc=linux-kernel@vger.kernel.org \
/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