From: Kazuya Mio <k-mio@sx.jp.nec.com>
To: ltp-list@lists.sourceforge.net
Subject: [LTP] ext4-online-defrag test doesn't work due to too old e4defrag command
Date: Thu, 24 Nov 2011 11:51:32 +0900 [thread overview]
Message-ID: <4ECDB134.3020706@sx.jp.nec.com> (raw)
Hi,
I tried to test ext4-online-defrag, but it didn't work well due to
the following errors:
ext4-online-defrag 0 TINFO : defrag type: 1, defrag obj: 2, block size: 1024
"/opt/ltp/testcases/bin/mnt_point/data0"
File is not regular file [ NG ]
Failed to defrag:Bad file descriptor [ NG ]
Failed to defrag:Bad file descriptor [ NG ]
<snip>
Failed to defrag:Bad file descriptor [ NG ]
Failed to defrag:Bad file descriptor [ NG ]
ext4-online-defrag 2 TPASS : ext4 online defrag test pass
This is because e4defrag is too old to defrag the file in the latest kernel.
I think we should use the latest e4defrag command that is contained in e2fsprogs.
Regards,
Kazuya Mio
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure
contains a definitive record of customers, application performance,
security threats, fraudulent activity, and more. Splunk takes this
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next reply other threads:[~2011-11-24 5:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-24 2:51 Kazuya Mio [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-11-28 5:25 [LTP] ext4-online-defrag test doesn't work due to too old e4defrag command Kazuya Mio
2011-11-30 7:26 ` Wanlong Gao
2011-11-30 8:34 ` Kazuya Mio
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=4ECDB134.3020706@sx.jp.nec.com \
--to=k-mio@sx.jp.nec.com \
--cc=ltp-list@lists.sourceforge.net \
/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