From: Akira Fujita <a-fujita@rs.jp.nec.com>
To: Ming Lei <Ming.Lei@riverbed.com>
Cc: "linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>,
Peng Chen <Peng.Chen@riverbed.com>
Subject: Re: Question of online defrag, thanks
Date: Tue, 29 Oct 2013 10:26:02 +0900 [thread overview]
Message-ID: <526F0EAA.10401@rs.jp.nec.com> (raw)
In-Reply-To: <2CE44BD3DBCF9541909CCB42F11CA3921C78E294@sfo1exc-mbxp08.nbttech.com>
Hello Ming,
> During running e4defrag, I am writing/reading data on file system.
> Is it safe to use e4defrag? I mean if power failure happens, is there any possibility of data loss or defragging file corruption?
# I have received same question from Peng and I already answered him. Anyway;
The journal feature and kernel internal locks protect data corruption
against power failure and R/W confliction on ext4, so you don't need to
worry about that.
For more detail about journal, please check
the following web page.
https://ext4.wiki.kernel.org/index.php/Ext4_Disk_Layout#Journal_.28jbd2.29
Regards,
Akira Fujita
(2013/10/29 2:13), Ming Lei wrote:
> Hi,
>
> I am using e4defrag to defrag running ext4 online.
> During running e4defrag, I am writing/reading data on file system.
> Is it safe to use e4defrag? I mean if power failure happens, is there any possibility of data loss or defragging file corruption?
> If there is possibility of defragging file corruption after power failure, can fsck fix it?
>
> Thank you very much.
> Peng
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2013-10-29 1:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-28 17:13 Question of online defrag, thanks Ming Lei
2013-10-29 1:26 ` Akira Fujita [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=526F0EAA.10401@rs.jp.nec.com \
--to=a-fujita@rs.jp.nec.com \
--cc=Ming.Lei@riverbed.com \
--cc=Peng.Chen@riverbed.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.