Re: [ANNOUNCE] xfs-linux: for-next updated to 6ef50fe9afae

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Mar 14, 2019 at 10:34:23PM -0700, Darrick J. Wong wrote:
> On Fri, Mar 15, 2019 at 11:50:36AM +0800, Zorro Lang wrote:
> > On Wed, Mar 13, 2019 at 09:32:43AM -0700, Darrick J. Wong wrote:
> > [3]
> > And Hit once generic/475 dmesg error on x86_64:
> > [29451.222118] XFS (dm-0): xfs_dabuf_map: bno 16777216 dir: inode 16797760
> > [29451.222123] XFS (dm-0): [00] br_startoff 16777216 br_startblock -2 br_blockcount 2 br_state 0
> 
> Hmm, a directory missing its bestfree blocks?
> 
> /me vaguely recalls arekm or someone had this failure a couple of weeks
> ago, but I've never seen 475 do this to me.

No, that was missing a the hash index tree root (block at 8MiFSB,
not 16MiFSB). Similar, but not the same.

Cheers,

Dave.
-- 
Dave Chinner
david@xxxxxxxxxxxxx



[Index of Archives]     [XFS Filesystem Development (older mail)]     [Linux Filesystem Development]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux RAID]     [Linux SCSI]


  Powered by Linux