From: Andreas Dilger <adilger@clusterfs.com>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Cc: Takashi Sato <sho@tnes.nec.co.jp>,
linux-ext4 <linux-ext4@vger.kernel.org>
Subject: Re: Online defragmentation
Date: Wed, 30 May 2007 08:10:34 -0600 [thread overview]
Message-ID: <20070530141034.GL5181@schatzie.adilger.int> (raw)
In-Reply-To: <465D2202.60600@linux.vnet.ibm.com>
On May 30, 2007 12:34 +0530, Aneesh Kumar K.V wrote:
> I haven't tested the defrag code. This came up when i was doing the
> online migration. With large file having large number of fragmented
> blocks I was getting the below error during the iput of the temporary
> inode.
>
> "ext4_free_blocks Freeing blocks not in datazone ...."
This shouldn't happen regardless of whether you are doing defrag or not,
since it will cause the filesystem to go read-only.
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.
prev parent reply other threads:[~2007-05-30 14:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-30 7:04 Online defragmentation Aneesh Kumar K.V
2007-05-30 7:48 ` Aneesh Kumar K.V
2007-05-31 4:05 ` Takashi Sato
2007-05-30 14:10 ` Andreas Dilger [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=20070530141034.GL5181@schatzie.adilger.int \
--to=adilger@clusterfs.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=linux-ext4@vger.kernel.org \
--cc=sho@tnes.nec.co.jp \
/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