linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ravi Pinjala <ravi@p-static.net>
To: linux-ext4@vger.kernel.org
Subject: e4defrag doesn't work on root filesystem
Date: Mon, 07 Sep 2009 10:48:01 -0500	[thread overview]
Message-ID: <4AA52B31.5090205@p-static.net> (raw)

Hi,

I'm playing with e4defrag from e2frprogs git, and I've run into a bug.
When I try to defragment files on my root filesystem, it refuses to
acknowledge that the filesystem is ext4. I believe the problem is that
it checks the filesystem type by parsing /etc/mtab, but the root
filesystem shows up there like this:

rootfs on / type rootfs (rw)
/dev/root on / type ext4 (rw,noatime,barrier=1,data=ordered)

so it gets confused by the bogus first entry. It works just fine on
other ext4 filesystems I have.

(If this is the wrong mailing list, I apologize; I couldn't find one for
e2fsprogs, so I thought this was the next best thing.)

--Ravi

             reply	other threads:[~2009-09-07 16:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-07 15:48 Ravi Pinjala [this message]
2009-09-08  3:55 ` e4defrag doesn't work on root filesystem Eric Sandeen
2009-09-08 13:42   ` Ravi Pinjala

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=4AA52B31.5090205@p-static.net \
    --to=ravi@p-static.net \
    --cc=linux-ext4@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).