Linux NILFS development
 help / color / mirror / Atom feed
From: Ivan Shmakov <oneingray-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: off-line resizing?
Date: Thu, 14 Jun 2012 11:22:17 +0700	[thread overview]
Message-ID: <86lijqv7ye.fsf@gray.siamics.net> (raw)
In-Reply-To: 20120614.110607.87804359.konishi.ryusuke@lab.ntt.co.jp

>>>>> Ryusuke Konishi writes:
>>>>> On Wed, 13 Jun 2012 23:06:54 +0700, Ivan Shmakov wrote:

[…]

 >> Unfortunately, I don't plan to switch my “production” hosts to Linux
 >> 3 yet.  However, for the purposes I want to give NILFS a try I can
 >> assume that I can easily umount the volume whenever I need to resize
 >> it, to run whatever user-space code necessary.

 >> Thus, I'm curious, are there any plans to implement “off-line” NILFS
 >> resizing?

 > Implementing Off-line resizing is a bit tough task because it
 > requires a user space library to read internal meta data of the nilfs
 > file system and append updated blocks to it.  This is almost
 > equivalent to implementing kernel functions of nilfs in user land.

 > So, we have no concrete schedule now.

	ACK, thanks.

	I wonder, how complicated this task would be?  In particular, do
	I need to alter all the segments to resize filesystem, or only
	specific ones?  Also, are these internal metadata records just
	“a bunch of C structs”, or something more complex?

[…]

 > For other Linux distros, the standalone kmod may be applicable with
 > or without customizing the source code.  it has a glue code to
 > support multiple kernel versions.  For reference, the source code of
 > the standalone kmod is available at:

 > git://github.com/nilfs-dev/nilfs2-kmod-centos6.git

	ACK, thanks.

-- 
FSF associate member #7257

--
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

  reply	other threads:[~2012-06-14  4:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-13 16:06 off-line resizing? Ivan Shmakov
     [not found] ` <86fw9zw601.fsf-Sxm0eyAyORm7AG94EA9mQA@public.gmane.org>
2012-06-14  2:06   ` Ryusuke Konishi
2012-06-14  4:22     ` Ivan Shmakov [this message]
     [not found]       ` <86lijqv7ye.fsf-Sxm0eyAyORm7AG94EA9mQA@public.gmane.org>
2012-06-16  1:15         ` Ryusuke Konishi
2012-06-17 15:44           ` user-level toolkit for off-line operations Ivan Shmakov

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=86lijqv7ye.fsf@gray.siamics.net \
    --to=oneingray-re5jqeeqqe8avxtiumwx3w@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox