public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: tytso@mit.edu
Cc: linux-ext4@vger.kernel.org
Subject: Re: [PATCH -V3 1/3] tune2fs: Make e2fsprogs handle ENOSPC better with inode resize
Date: Thu, 6 Aug 2009 11:48:58 +0530	[thread overview]
Message-ID: <20090806061858.GA3344@skywalker> (raw)
In-Reply-To: <1249539151-3191-1-git-send-email-aneesh.kumar@linux.vnet.ibm.com>

Hi,

I tested this series with the following usecase:

  a) using mkfs create a badblock map and see if the inode resize fail if
     it find a mapping blocks as bad block.
  b) On resizing inode if we find the mapping block having block bitmap
    or inode bitmap we make sure we find a block in the same group. Used
    debugfs set_bg to force a block bitmap after inode table.
  c) If not we fail the inode resize
  d) If we don't have enough space left we fail inode resize.


-aneesh

  parent reply	other threads:[~2009-08-06  6:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-06  6:12 [PATCH -V3 1/3] tune2fs: Make e2fsprogs handle ENOSPC better with inode resize Aneesh Kumar K.V
2009-08-06  6:12 ` [PATCH -V3 2/3] tune2fs: Handle fs meta-data blocks during " Aneesh Kumar K.V
2009-08-06  6:12 ` [PATCH -V3 3/3] tune2fs: handle bad blocks when resizing inodes Aneesh Kumar K.V
2009-08-06  6:18 ` Aneesh Kumar K.V [this message]
2009-08-20  7:06 ` [PATCH -V3 1/3] tune2fs: Make e2fsprogs handle ENOSPC better with inode resize Aneesh Kumar K.V
2009-08-21 12:25   ` Theodore Tso

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=20090806061858.GA3344@skywalker \
    --to=aneesh.kumar@linux.vnet.ibm.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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