On Fri, Aug 5, 2011 at 11:40 AM, Greg Freemyer <greg.freemyer@xxxxxxxxx> wrote:
> On Fri, Aug 5, 2011 at 9:53 AM, Amir Goldstein <amir73il@xxxxxxxxx> wrote:
>> Hi Anand,
>> Can you please post the patch in the body of the message so we can
>> comment on it inline.
>> Aditya is also working on a btrfs snapshots xfstest (currently named
>> 257) as part of
>> his Google summer of code project.
>> It would be great if you guys can cooperate your efforts.
>> BTW, while running Aditya's test, Greg has stumbled upon a btrfs OOPS.
>> Greg can provide more details about it.
>> On Fri, Aug 5, 2011 at 10:59 AM, Anand Jain <Anand.Jain@xxxxxxxxxx> wrote:
>>> Attached is the patch for the xfstests, which adds snapshot,
>>> defragment and volume management test cases for the btrfs
>>> (257, 258 and 259 respectively).
>>> This introduces a new user variable 'DISK_POOL' which should
>>> be set to disks for the raid tests.
>>> An example of usage of these tests is as below.
>>> [root@localhost xfstests]# cat local.config
>>> DISK_POOL="/dev/sdf /dev/sdg"
>>> [root@localhost xfstests]#
>>> [root@localhost xfstests]# ./check 257 258 259
>>> FSTYP -- btrfs
>>> PLATFORM -- Linux/i686 localhost 3.0.0-rc6+
>>> MKFS_OPTIONS -- /dev/sde
>>> MOUNT_OPTIONS -- -o context=system_u:object_r:nfs_t:s0 /dev/sde /btrfs1
>>> 257 8s
>>> 258 3s
>>> 259 33s
>>> Ran: 257 258 259
>>> Passed all 3 tests
>>> Thank you.
> I've only reproduced the oops in 2.6.39 and older using openSUSE 11.4
> I have not tried with 3.0 or newer nor with newer userspace, so it may
> or may not have been fixed.
> It happened with a openSUSE kernel, so I put it in their bugzilla.
I just tested with kernel 3.0 and the oops is gone.
I closed that bugzilla as resolved.