linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Theodore Tso <tytso@mit.edu>
To: Eric Sandeen <sandeen@redhat.com>
Cc: ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH] debugfs: open with EXT2_FLAG_64BITS
Date: Mon, 26 Oct 2009 01:15:55 -0400	[thread overview]
Message-ID: <20091026051555.GA13941@mit.edu> (raw)
In-Reply-To: <4ACE48BC.7010505@redhat.com>

On Thu, Oct 08, 2009 at 03:17:00PM -0500, Eric Sandeen wrote:
> Eric Sandeen wrote:
> > Pointing debugfs from the pu branch at a large filesystem is
> > still failing with:
> > 
> >  Filesystem too large to use legacy bitmaps while reading block bitmap
> > 
> > We need to open with EXT2_FLAG_64BITS; I'm not sure if this
> > should be a switch based on the size of the fs or not?
> > 
> > But in any case the below gets things moving enough to
> > use debugfs on a large filesystem.
> 
> ping?

I've added this patch to the pu branch.  I've also updated the pu
branch so it's up to date with the latest maint branch.  I also found
some missing conversions of ext2fs_group_{first,last}_block() to
ext2fs_group_{first,last}_block2().  

I also cleaned up a number of patches which I'm confident enough are
clean enough that I've fast forwarded the next branch to include them.

There are now only 16 patches left that are unique to the pu branch,
down from 57 patches initially (and many of the patches are smaller as
they were refactored).

						- Ted

      reply	other threads:[~2009-10-26  5:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-11 15:18 [PATCH] debugfs: open with EXT2_FLAG_64BITS Eric Sandeen
2009-09-12 20:29 ` Andreas Dilger
2009-10-08 20:17 ` Eric Sandeen
2009-10-26  5:15   ` Theodore Tso [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=20091026051555.GA13941@mit.edu \
    --to=tytso@mit.edu \
    --cc=linux-ext4@vger.kernel.org \
    --cc=sandeen@redhat.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;
as well as URLs for NNTP newsgroup(s).