From: Chris Mason <mason@suse.com>
To: Oleg Drokin <green@namesys.com>
Cc: Nick Burrett <nick@dsvr.net>, reiserfs-list@namesys.com
Subject: Re: symlink has wrong sd_blocks count
Date: 18 Feb 2003 07:56:26 -0500 [thread overview]
Message-ID: <1045572986.13746.3.camel@tiny.suse.com> (raw)
In-Reply-To: <20030218144243.A6891@namesys.com>
On Tue, 2003-02-18 at 06:42, Oleg Drokin wrote:
> Hello!
>
> On Tue, Feb 18, 2003 at 10:53:25AM +0000, Nick Burrett wrote:
>
> > I'm running a stock 2.4.20 kernel with the reiserfs quota patches applied.
> > Simply creating a symlink and then running reiserfsck shows errors like
> > this:
> > /foofile 2 4 has wrong sd_blocks 8, has to be 1
> > I've reproduced this 100% on 100 filesystems on two servers.
>
> Aha, I see.
> Ignore this message for now for directories and symlinks.
> This is because when reiserfs calculates number of blocks file would use,
> in case of no quota, reiserfs code does this and can do this precisely
> (up to 512 bytes), but with quota patches applied, quota code takes
> account of blocks used. And it round everything up to blocksize, hence
> the difference. And reiserfsck uses only 1st variant of the code.
> I am not yet sure on how to deal with the issue.
> Just ignore this message for now.
The quota code can have special checks for symlinks, but the sd_block
accounting is somewhat complex, and I've been hesitant to make it even
more so with the symlink checks.
-chris
next prev parent reply other threads:[~2003-02-18 12:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-18 10:53 symlink has wrong sd_blocks count Nick Burrett
2003-02-18 11:42 ` Oleg Drokin
2003-02-18 12:56 ` Chris Mason [this message]
2003-02-18 13:37 ` Oleg Drokin
2003-02-18 13:41 ` Chris Mason
2003-02-18 13:43 ` Oleg Drokin
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=1045572986.13746.3.camel@tiny.suse.com \
--to=mason@suse.com \
--cc=green@namesys.com \
--cc=nick@dsvr.net \
--cc=reiserfs-list@namesys.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.