Re: xfs problem

[Timothy Shimmin <tes@xxxxxxx>]

Hi Yogesh,

I'm sorry for your 2nd crash :(
It's not so simple to "up the reservation" because we really need to 
know why this was a problem and we don't have a sense of
by how much it needs to be increased.
Can you build a kernel with XFS_LOG_RES_DEBUG defined?
If this is defined then a lot more information will be printed out on 
the next such error:
e.g. the transaction type, reservation size and the component regions 
and their sizes which make up the transaction etc.

--Tim

Yogesh Bhanu wrote:
> Hi ,
>         Its my second crash in 14 days, again the system spewed a 
> similar error message for reservation failure .
> This is a bit disconcerting as we are in middle of migration from our 
> old fileservers.  Is there a way I can up the reservation.
> Output of /var/log/messges
> -------------cut here-----------------------
> Oct 21 11:58:02 mipsopt-02 kernel: Filesystem "dm-0": xfs_log_write: 
> reservation ran out. Need to up reservation
> Oct 21 11:58:02 mipsopt-02 kernel: xfs_force_shutdown(dm-0,0x8) called 
> from line 1689 of file fs/xfs/xfs_log.c.  Return address = 
> 0xffffffffa01b45e8
> Oct 21 11:58:02 mipsopt-02 kernel: Filesystem "dm-0": Corruption of 
> in-memory data detected.  Shutting down filesystem: dm-0
> Oct 21 11:58:02 mipsopt-02 kernel: Please umount the filesystem, and 
> rectify the problem(s)
> Oct 21 11:58:02 mipsopt-02 kernel: xfs_force_shutdown(dm-0,0x2) called 
> from line 1284 of file fs/xfs/xfs_log.c.  Return address = 
> 0xffffffffa01b45e8
> -------------cut here-----------------------
> Thanks
> yogesh