From: Matteo Frigo <athena-/JWCw35jmeM@public.gmane.org>
To: linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: resizing file system
Date: Sat, 11 Sep 2010 05:46:29 -0400 [thread overview]
Message-ID: <87iq2cr4sq.fsf_-_@fftw.org> (raw)
In-Reply-To: 20090408.023005.48479195.ryusuke@osrg.net
Ryusuke Konishi <ryusuke-sG5X7nlA6pw@public.gmane.org> writes:
> An experimental resize feature did exist, but it's not applicable to
> the current version. And, it didn't support shrinking.
> So the feature you want is not available now. (Sorry for inconvenience)
Ryusuke,
Thanks for developing nilfs2, it is a superb piece of work.
I am interested in the resize feature and willing to implement it, but I
need a little help. My understanding of the nilfs2 source code in
2.6.35.4 is that in order to grow a file system it should be sufficient
to change s_nsegments in both superblocks while the file system is
unmounted. If I understand correctly, the sufile grows automatically to
accomodate the additional segments because nilfs_sufile_alloc() calls
nilfs_sufile_get_segment_usage_block() with create=1, which grows the
sufile as necessary.
Is this interpretation correct? If so, it should not be too hard to
code a little utility that grows an unmounted file system. (Later we'll
worry about shrinking and online resize.)
You allude to an experimental resize feature. Do you have code that I
can adapt to the current version?
Thanks,
Matteo Frigo
--
To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-09-11 9:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-07 16:57 [SPAM] resizing file system Munro, Fred
[not found] ` <BAEFA5609CC3AB4BAE1625CAD4C27E5C02986E1D-qPLjlnsG5hmCmmEZ8mJCX5vx1ZQ4fP860E9HWUfgJXw@public.gmane.org>
2009-04-07 17:30 ` Ryusuke Konishi
[not found] ` <20090408.023005.48479195.ryusuke-sG5X7nlA6pw@public.gmane.org>
2009-04-07 17:40 ` Munro, Fred
2010-09-11 9:46 ` Matteo Frigo [this message]
[not found] ` <87iq2cr4sq.fsf_-_-/JWCw35jmeM@public.gmane.org>
2010-09-11 18:34 ` Ryusuke Konishi
2010-09-11 19:40 ` [PATCH] Compare device number rather than device name for mount check Matteo Frigo
[not found] ` <87d3skgjc3.fsf_-_-/JWCw35jmeM@public.gmane.org>
2010-09-12 3:35 ` Ryusuke Konishi
2010-09-11 23:31 ` resizing file system Matteo Frigo
[not found] ` <87zkvnoo1l.fsf-/JWCw35jmeM@public.gmane.org>
2010-09-12 2:26 ` Ryusuke Konishi
[not found] ` <20100912.112650.179928857.ryusuke-sG5X7nlA6pw@public.gmane.org>
2010-09-17 9:15 ` Jiro SEKIBA
[not found] ` <87tylo7msw.wl%jir-27yqGEOhnJbQT0dZR+AlfA@public.gmane.org>
2010-09-17 16:20 ` Ryusuke Konishi
[not found] ` <20100918.012000.159151572.ryusuke-sG5X7nlA6pw@public.gmane.org>
2010-09-27 10:59 ` Jiro SEKIBA
[not found] ` <87fwwvo3it.wl%jir-27yqGEOhnJbQT0dZR+AlfA@public.gmane.org>
2010-09-27 16:01 ` Ryusuke Konishi
[not found] ` <20100928.010138.179946334.ryusuke-sG5X7nlA6pw@public.gmane.org>
2010-10-01 4:21 ` Jiro SEKIBA
[not found] ` <87wrq2tufd.wl%jir-27yqGEOhnJbQT0dZR+AlfA@public.gmane.org>
2010-10-03 10:34 ` Ryusuke Konishi
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=87iq2cr4sq.fsf_-_@fftw.org \
--to=athena-/jwcw35jmem@public.gmane.org \
--cc=linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 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.