Re: FileFallocate misbehaving on XFS

On 2024-12-10 11:34:15 -0500, Andres Freund wrote:
> On 2024-12-10 12:36:33 +0100, Jakub Wartak wrote:
> >  On Tue, Dec 10, 2024 at 7:34 AM Michael Harris <harmic@gmail.com> wrote:
> > 2.
> > 
> > > # xfs_info /dev/mapper/ippvg-ipplv
> > > meta-data=/dev/mapper/ippvg-ipplv isize=512    agcount=4,
> > agsize=262471424 blks
> > >         =                       sectsz=512   attr=2, projid32bit=1
> > >         =                       crc=1        finobt=0, sparse=0, rmapbt=0
> > >         =                       reflink=0    bigtime=0 inobtcount=0
> > nrext64=0
> > 
> > Yay, reflink=0, that's pretty old fs ?!
> 
> I think that only started to default to on more recently (2019, plus time to
> percolate into RHEL). The more curious cases is finobt=0 (turned on by default
> since 2015) and to a lesser degree sparse=0 (turned on by default since 2018).

One thing that might be interesting is to compare xfs_info of affected and
non-affected servers...