On Thu, Mar 06, 2008 at 11:29:07PM -0500, Chris Knadle wrote:
> During the final unmount before reboot there was an assertion failure from
> XFS
> leading to the debug output below; I've included what was available on the
> screendump, which I handwrote + transcribed. [I also have screenshots from a
> 2.1 MP camera -- they're slightly ugly but usable.] CONFIG_KEXEC was not
> compiled in, so I was uanble to get a crashdump via SysRq. I'm sending this
> along in case someone working on the XFS fs can find + fix a bug. I'm not
> sending the kernel config in this first post just as not to spam everybody
> with it if it's not needed -- if desired just ask and I'll send it.
> Source used: 2.6.24.y from git -- 2.6.24.3.
>
> This is on my Desktop box, x86 system -- single P4 CPU @ 2.6 GHz, IDE disk
> attached to an onboard HighPoint HPT370 controller, and running Debian Sid.
>
> When replying please CC me, as I am not currently subscribed to the list.
......
> Assertion failed: atomic_read(&mp->m_active_trans) == 0, file:
> fs/xfs/xfs_vfsops.c, line: 708
Known problem. Race in the VFS w.r.t. read-only remounts:
http://marc.info/?l=linux-kernel&m=120106649923499&w=2
The fix for the problem lies outside XFS:
http://marc.info/?l=linux-kernel&m=120109304227035&w=2
Cheers,
Dave.
--
Dave Chinner
Principal Engineer
SGI Australian Software Group
|