linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Sterba <dave@jikos.cz>
To: ching <lsching17@gmail.com>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs defrag problem
Date: Wed, 31 Oct 2012 01:40:27 +0100	[thread overview]
Message-ID: <20121031004027.GE3102@twin.jikos.cz> (raw)
In-Reply-To: <508FBE50.6070300@gmail.com>

On Tue, Oct 30, 2012 at 07:47:28PM +0800, ching wrote:
>     failed to open /bin/bash
>     open:: Text file busy

That's not a btrfs problem, you can't directly modify an executable that
is being used.

>     failed to open /lib64/ld-2.15.so
>     failed to open /sbin/agetty
>     failed to open /sbin/btrfs
>     failed to open /sbin/dhclient
>     failed to open /sbin/init
>     failed to open /sbin/udevd

libraries, currently executed progs or daemons

>     It seems that locked files cannot be defragged, is it expected behaviour?

Yes.

> 2. Btrfs Wiki mentions that defrag directory will defrag metadata, is symlink/hardlink considered as metadata?
>     P.S. inline data is already disabled by "max_inline=0"

Both -links are metadata and also stored inside metadata blocks without
any chance to move to data blocks, so max_inline does not affect this.

> 3. Is any possible to online defrag a btrfs partition without hindered by mount point/polyinstantied directories?

Sorry, I do not understand the question.

david

  parent reply	other threads:[~2012-10-31  0:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-30 11:47 btrfs defrag problem ching
2012-10-30 12:08 ` cwillu
2012-10-31  0:14   ` ching
2012-10-31  0:40 ` David Sterba [this message]
2012-10-31 21:17   ` ching
2012-11-05 22:57     ` David Sterba
2012-11-05 23:48       ` ching
2012-11-06 13:49       ` Sander

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=20121031004027.GE3102@twin.jikos.cz \
    --to=dave@jikos.cz \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=lsching17@gmail.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).