linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: hooanon05@yahoo.co.jp
To: Andrew Morton <akpm@linux-foundation.org>,
	tomas@slax.org, linux-kernel@vger.kernel.org,
	akinobu.mita@gmail.com, util-linux-ng@vger.kernel.org
Subject: Re: [PATCH] loop file resizable
Date: Fri, 21 Nov 2008 12:19:06 +0900	[thread overview]
Message-ID: <7464.1227237546@jrobl> (raw)
In-Reply-To: <7027.1227235078@jrobl>


hooanon05@yahoo.co.jp:
> 
> Andrew Morton:
> > Well if we're going to do this then I guess we'll need to tell the
> > util-linux people about it, as users will be needing some tool with
> > which to access the new fucntionality.
	:::

> Here is the utility named logrow.

I should left some notes here.
Several people uses truncate/ftruncate to expand the size of the backend
file. Actually I used to do it. In this version of logrow.c, I changed
it to write, in order to allocate the disk blocks.

If I issued truncate and expand the size of filesystem by xfs_growfs or
something, it would succeed. But when the filesystem which has the
backend file becomes full and the loopback mounted xfs wants more disk
blocks, it will return EIO or retry several times.
I believe it should return ENOSPC at once and changed to write garbages
and allocate the disk blocks.

Tomas, this is the point of the new version.


J. R. Okajima

  reply	other threads:[~2008-11-21  3:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-17  7:44 [PATCH] loop file resizable Tomas M
2008-11-19  0:42 ` Andrew Morton
2008-11-19  2:07   ` Akinobu Mita
2008-11-19  3:51   ` hooanon05
2008-11-19 18:34     ` Tomas M
2008-11-20 21:26     ` Andrew Morton
2008-11-21  2:37       ` hooanon05
2008-11-21  3:19         ` hooanon05 [this message]
2008-11-21  4:31       ` [PATCH v2] " hooanon05
2008-11-21 10:12       ` [PATCH] " Karel Zak
2008-11-21 12:23         ` hooanon05
2008-11-21 12:44           ` Karel Zak
2008-11-24  2:08             ` hooanon05

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=7464.1227237546@jrobl \
    --to=hooanon05@yahoo.co.jp \
    --cc=akinobu.mita@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tomas@slax.org \
    --cc=util-linux-ng@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;
as well as URLs for NNTP newsgroup(s).