From: Blaisorblade <blaisorblade@yahoo.it>
To: Alex Zarochentsev <zam@namesys.com>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org,
reiserfs-dev@namesys.com, reiserfs-list@namesys.com,
mtk-manpages@gmx.net
Subject: Re: [patch 1/1] reiserfs: make resize option auto-get new device size
Date: Fri, 8 Apr 2005 10:23:07 +0200 [thread overview]
Message-ID: <200504081023.09343.blaisorblade@yahoo.it> (raw)
In-Reply-To: <20050408081047.GX6211@backtop.namesys.com>
On Friday 08 April 2005 10:10, Alex Zarochentsev wrote:
> Hi,
>
> On Fri, Apr 08, 2005 at 06:55:50AM +0200, blaisorblade@yahoo.it wrote:
> > Cc: <reiserfs-dev@namesys.com>, <reiserfs-list@namesys.com>,
> > <mtk-manpages@gmx.net>
> >
> > It's trivial for the resize option to auto-get the underlying device
> > size, while it's harder for the user. I've copied the code from jfs.
> >
> > Since of the different reiserfs option parser (which does not use the
> > superior match_token used by almost every other filesystem), I've had to
> > use the "resize=auto" and not "resize" option to specify this behaviour.
> > Changing the option parser to the kernel one wouldn't be bad but I've no
> > time to do this cleanup in this moment.
>
> do people really need it?
Note we are speaking of 2 lines of code. And there's no point in omitting
this.
> user-level utility reisize_reiserfs, being called w/o size argument,
> calculates the device size and uses resize mount option with correct value.
Yes, I know this. But the old versions (the one shipped on Mdk) didn't work
for online resizing (this was verified by me with lots of warnings and a Oops
on reiserfs code); in fact, this ability is so new that is not even
documented in manpages.
--
Paolo Giarrusso, aka Blaisorblade
Linux registered user n. 292729
http://www.user-mode-linux.org/~blaisorblade
prev parent reply other threads:[~2005-04-08 8:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-08 4:55 blaisorblade
2005-04-08 8:10 ` Alex Zarochentsev
2005-04-08 8:23 ` Blaisorblade [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=200504081023.09343.blaisorblade@yahoo.it \
--to=blaisorblade@yahoo.it \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtk-manpages@gmx.net \
--cc=reiserfs-dev@namesys.com \
--cc=reiserfs-list@namesys.com \
--cc=zam@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®