From: Kazuya Mio <k-mio@sx.jp.nec.com>
To: "Steinar H. Gunderson" <sgunderson@bigfoot.com>
Cc: a-fujita@rs.jp.nec.com, linux-ext4@vger.kernel.org
Subject: Re: Segmentation fault in e4defrag -c
Date: Fri, 26 Jun 2009 17:32:48 +0900 [thread overview]
Message-ID: <4A4487B0.9080000@sx.jp.nec.com> (raw)
In-Reply-To: <20090625105558.GA21773@uio.no>
Hi Steinar,
Thanks for testing defrag.
e4defrag -c works fine in the case without defrag patch.
I cannot reproduce this problem, so I think this problem occurred in unusual
cases (e.g. i_size is not zeroed but it has no extent)
To solve this problem, could you send me the following information?
1. mount option of /home/sesse
2. filefrag -v "/home/sesse/Mika - Life In Cartoon Motion/11 - Ring Ring (Bonus
Track).mp3"
3. stat "/home/sesse/Mika - Life In Cartoon Motion/11 - Ring Ring (Bonus Track).mp3"
Does this problem occur at all times?
Regards,
Kazuya Mio
next prev parent reply other threads:[~2009-06-26 8:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-25 10:55 Segmentation fault in e4defrag -c Steinar H. Gunderson
2009-06-26 8:32 ` Kazuya Mio [this message]
2009-06-26 9:38 ` Steinar H. Gunderson
2009-06-29 6:03 ` Akira Fujita
2009-06-29 21:49 ` Andreas Dilger
2009-06-30 23:43 ` Akira Fujita
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=4A4487B0.9080000@sx.jp.nec.com \
--to=k-mio@sx.jp.nec.com \
--cc=a-fujita@rs.jp.nec.com \
--cc=linux-ext4@vger.kernel.org \
--cc=sgunderson@bigfoot.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).