From: Eric Sandeen <sandeen@redhat.com>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Theodore Tso <tytso@mit.edu>,
Ext4 Developers List <linux-ext4@vger.kernel.org>,
Jan Kara <jack@suse.cz>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: Regression with ext4 in kernel 2.6.39-rc7? (Was: testing ext4 master branch)
Date: Fri, 13 May 2011 12:28:13 -0500 [thread overview]
Message-ID: <4DCD6A2D.30504@redhat.com> (raw)
In-Reply-To: <BANLkTim8ihBNzxxkoTwigKMQB1xHToevdQ@mail.gmail.com>
On 5/13/11 12:25 PM, Amir Goldstein wrote:
> On Fri, May 13, 2011 at 6:25 PM, Eric Sandeen <sandeen@redhat.com> wrote:
>> On 5/13/11 9:56 AM, Ted Ts'o wrote:
>>> On Fri, May 13, 2011 at 12:17:03PM +0300, Amir Goldstein wrote:
>>>>
>>>> Can anyone try to reproduce the error with xfstest 005 and the crash
>>>> with xfstest 232?
>>>
>>> Xfstest #5 broke because of a change in the VFS, which now allows up
>>> to 40 nested symlinks. So that's a matter of your xfstests being too
>>> old.
>>>
>>> The version of xfstests I've been using on my KVM box is too old to
>>> have test 232, so I haven't been able to test it. I've been trying to
>>> use a newer version of xfstests, but xfstests doesn't build on either
>>> Ubuntu 10.04 (LTS), Debian stable, or Debian unstable, due to the use
>>> of newer XFS ioctl's and xfsctl's that aren't defined in the system
>>> header files. The fact that it doesn't work on Ubuntu LTS and Stable
>>> is not that surprising, I suppose, but I was a bit disappointed that
>>> it doesn't work on Debian unstable.
>>
>> I missed that bug report :) If you can send me the details of the
>> failures we can probably add configure tests for any new ioctls
>> that are causing build failures.
>>
>>> Since I don't have a Fedora system handy --- which header file are
>>> things like "struct xfs_flock64" supposed to be defined these days?
>>
>> Hm, well, on my Fedora system, /usr/include/xfs/xfs_fs.h, from xfsprogs-devel.
>>
>> I don't think that has changed in a very long time...
>>
>> I also package an xfsprogs-qa-devel which has some additional pieces in
>> it to support xfstests. Debian could do the same ... "make install-qa"
>> in xfsprogs puts those bits into the root.
>>
>
> After xfstests failed to build on Ubuntu 10.10, I followed the advice omitted
> by the build script to run "make install-qa", to solve the problem.
> It took me a while to figure exactly where I should run the command,
> but in the end I pulled the xfsprogs tree, ran "make; make install;
> make install-qa"
> and from there on things were looking better.
I can ask Nathan if he can package the qa bits for debian.
Or, you all could just use Fedora ;)
-Eric
next prev parent reply other threads:[~2011-05-13 17:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-13 9:17 Regression with ext4 in kernel 2.6.39-rc7? (Was: testing ext4 master branch) Amir Goldstein
2011-05-13 9:27 ` Sedat Dilek
2011-05-13 10:34 ` Amir Goldstein
2011-05-13 14:56 ` Ted Ts'o
2011-05-13 15:25 ` Eric Sandeen
2011-05-13 17:25 ` Amir Goldstein
2011-05-13 17:28 ` Eric Sandeen [this message]
2011-05-13 17:31 ` Eric Sandeen
2011-05-13 17:37 ` Amir Goldstein
2011-05-13 22:49 ` Ted Ts'o
2011-05-14 7:11 ` Amir Goldstein
2011-05-14 10:16 ` Amir Goldstein
2011-05-16 9:43 ` Jan Kara
2011-05-16 9:59 ` Amir Goldstein
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=4DCD6A2D.30504@redhat.com \
--to=sandeen@redhat.com \
--cc=amir73il@gmail.com \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=tytso@mit.edu \
/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.