From: "Steinar H. Gunderson" <sgunderson@bigfoot.com>
To: Kazuya Mio <k-mio@sx.jp.nec.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 11:38:16 +0200 [thread overview]
Message-ID: <20090626093816.GA3175@uio.no> (raw)
In-Reply-To: <4A4487B0.9080000@sx.jp.nec.com>
On Fri, Jun 26, 2009 at 05:32:48PM +0900, Kazuya Mio wrote:
> e4defrag -c works fine in the case without defrag patch.
I tried 2.6.31-rc1 now (which should have the defrag patch, right?).
There's no change -- and it still cannot actually defrag for some reason.
> To solve this problem, could you send me the following information?
> 1. mount option of /home/sesse
/dev/mapper/pannekake-home on /home type ext4 (rw,errors=remount-ro)
> 2. filefrag -v "/home/sesse/Mika - Life In Cartoon Motion/11 - Ring
> Ring (Bonus Track).mp3"
pannekake:~# filefrag -v "/home/sesse/Mika - Life In Cartoon Motion/11 - Ring Ring (Bonus Track).mp3"
Checking /home/sesse/Mika - Life In Cartoon Motion/11 - Ring Ring (Bonus Track).mp3
Filesystem type is: ef53
Filesystem cylinder groups is approximately 315
File is stored in extents format
Blocksize of file /home/sesse/Mika - Life In Cartoon Motion/11 - Ring Ring (Bonus Track).mp3 is 4096
File size of /home/sesse/Mika - Life In Cartoon Motion/11 - Ring Ring (Bonus Track).mp3 is 4050385 (989 blocks)
First block: 0
Last block: 0
/home/sesse/Mika - Life In Cartoon Motion/11 - Ring Ring (Bonus Track).mp3: 1 extent found
> 3. stat "/home/sesse/Mika - Life In Cartoon Motion/11 - Ring Ring (Bonus Track).mp3"
pannekake:~# stat "/home/sesse/Mika - Life In Cartoon Motion/11 - Ring Ring (Bonus Track).mp3"
File: `/home/sesse/Mika - Life In Cartoon Motion/11 - Ring Ring (Bonus Track).mp3'
Size: 4050385 Blocks: 0 IO Block: 4096 regular file
Device: fd12h/64786d Inode: 688755 Links: 1
Access: (0644/-rw-r--r--) Uid: ( 1000/ sesse) Gid: ( 1000/ sesse)
Access: 2009-05-30 03:08:38.724454316 +0200
Modify: 2008-09-01 20:38:26.135589449 +0200
Change: 2008-09-01 20:38:26.135589449 +0200
> Does this problem occur at all times?
Yes, it's 100% consistent on that file.
/* Steinar */
--
Homepage: http://www.sesse.net/
next prev parent reply other threads:[~2009-06-26 9:38 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
2009-06-26 9:38 ` Steinar H. Gunderson [this message]
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=20090626093816.GA3175@uio.no \
--to=sgunderson@bigfoot.com \
--cc=a-fujita@rs.jp.nec.com \
--cc=k-mio@sx.jp.nec.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.