On Fri, Jul 11, 2008 at 09:46:47AM +0200, Mikael Abrahamsson wrote:
> I received this when running xfs_fsr to defragment my xfs volume (which
> resides on a crypted lvm).
Hmmmm. XFS has a history of triggering unique bugs in crypted
volumes - thank you for letting us know up front that this is
what you are using.
> Could it be that something is wrong with my xfs volume and this is not
> being properly handled (since it seems to refer to getbmap below?).
Could be - xfs_check will tell you if there is anything wrong with
> Kernel is configured with oldconfig from ubuntu hardy stock kernel plus
> Alsa. Hardware can be seen at
> Kernel oopsed (caps lock+other flashing when I woke up this morning),
> don't know if it's related to the below bug or if it's something else.
> Screensaver was on so I couldn't see any text to see more info.
> Jul 8 04:44:56 via kernel: [554197.888008] ------------[ cut here
> Jul 8 04:44:56 via kernel: [554197.888008] kernel BUG at
> Jul 8 04:44:56 via kernel: [554197.888008] invalid opcode: 0000 [#1] SMP
> Jul 8 04:44:56 via kernel: [554197.888008] Modules linked in: soundcore
> ac97_bus isofs udf crc_itu_t nvidia(P) af_packet rfcomm l2c
That could also be a factor.
> Pid: 16200, comm: xfs_fsr Tainted: P (2.6.26-rc8 #1)
> EIP: 0060:[<f956201b>] EFLAGS: 00010282 CPU: 0
> EIP is at assfail+0x1b/0x20 [xfs]
Oh - you must be running a debug XFS. CONFIG_XFS_DEBUG was only
introduced in 2.6.26-rc1 and defaults to 'N', so you must have
selected the non-default option when prompted. This will cause your
machine to oops at the slightest inconsistency that is found,
regardless of whether it is fatal or not. Like the help text says,
don't set this unless you are an XFS developer....
That aside, what was the assert failure reported prior to the oops? i.e.
paste the lines in the log before the ---[ cut here ]--- line?
One of them will start with 'Assertion failed:', I think....