On Wed, Dec 21, 2011 at 3:34 AM, Dave Chinner <david@xxxxxxxxxxxxx> wrote:
> On Tue, Dec 20, 2011 at 07:18:15PM +0530, Amit Sahrawat wrote:
>> While trying to open a file with a large number of extents in append
>> mode – it resulted in the below error logs continually.
>> I was trying to open the file in append mode, but it showed error, so
>> I checked for the extents – it has around 2238 extents. Although, it
> The first question you have to get to the bottom of is if there are
> only 2238 extents in the file, why is the xfs_bmap output showing
> more than that?
Actually the output got mismatched, 2238 was the number when I checked
the issue, while xfs_bmap results were for the last traces observed.
Sorry for the confusion.
>> is not repetitive, when I try on next mount and write – it is working
>> fine at times.
>> Also, the system does not seem to be corrupted. Since, running
>> xfs_repair after umount does not show any errors.
> Which implies memory corruption. Have you turned on memory poisoning
> and the memory leak detection to see if it detects any problems?
> What about running with CONFIG_XFS_DEBUG=y? Does that trip any
> problems sooner than the corruption is detected?
I will try with CONFIG_XFS_DEBUG.
Thanks & Regards,
> Dave Chinner