On Thu, Mar 18, 2021 at 03:19:01PM -0700, Darrick J. Wong wrote: > On Fri, Mar 19, 2021 at 07:55:36AM +1100, Dave Chinner wrote: > > On Thu, Mar 18, 2021 at 12:17:06PM -0400, Brian Foster wrote: > > > perag reservation is enabled at mount time on a per AG basis. The > > > upcoming in-core allocation btree accounting mechanism needs to know > > > when reservation is enabled and that all perag AGF contexts are > > > initialized. As a preparation step, set a flag in the mount > > > structure and unconditionally initialize the pagf on all mounts > > > where at least one reservation is active. > > > > I'm not sure this is a good idea. AFAICT, this means just about any > > filesystem with finobt, reflink and/or rmap will now typically read > > every AGF header in the filesystem at mount time. That means pretty > > much every v5 filesystem in production... > > They already do that, because the AG headers are where we store the > btree block counts. Oh, we're brute forcing AG reservation space? I thought we were doing something smarter than that, because I'm sure this isn't the first time I've mentioned this problem.... > > We've always tried to avoid needing to reading all AG headers at > > mount time because that does not scale when we have really large > > filesystems (I'm talking petabytes here). We should only read AG > > headers if there is something not fully recovered during the mount > > (i.e. slow path) and not on every mount. > > > > Needing to do a few thousand synchonous read IOs during mount makes > > mount very slow, and as such we always try to do dynamic > > instantiation of AG headers... Testing I've done with exabyte scale > > filesystems (>10^6 AGs) show that it can take minutes for mount to > > run when each AG header needs to be read, and that's on SSDs where > > the individual read latency is only a couple of hundred > > microseconds. On spinning disks that can do 200 IOPS, we're > > potentially talking hours just to mount really large filesystems... > > Is that with reflink enabled? Reflink always scans the right edge of > the refcount btree at mount to clean out stale COW staging extents, Aren't they cleaned up at unmount when the inode is inactivated? i.e. isn't this something that should only be done on a unclean mount? > and > (prior to the introduction of the inode btree counts feature last year) > we also ahad to walk the entire finobt to find out how big it is. ugh, I forgot about the fact we had to add that wart because we screwed up the space reservations for finobt operations... As for large scale testing, I suspect I turned everything optional off when I last did this testing, because mkfs currently requires a lot of per-AG IO to initialise structures. On an SSD, mkfs.xfs -K -f -d agcount=10000 ... takes mkfs time mount time -m crc=0 15s 1s -m rmapbt=1 25s 6s Multiply those times by at another 1000 to get to an 8EB filesystem and the difference is several hours of mkfs time and a couple of hours of mount time.... So from the numbers, it is pretty likely I didn't test anything that actually required iterating 8 million AGs at mount time.... > TBH I think the COW recovery and the AG block reservation pieces are > prime candidates for throwing at an xfs_pwork workqueue so we can > perform those scans in parallel. As I mentioned on #xfs, I think we only need to do the AG read if we are near enospc. i.e. we can take the entire reservation at mount time (which is fixed per-ag) and only take away the used from the reservation (i.e. return to the free space pool) when we actually access the AGF/AGI the first time. Or when we get a ENOSPC event, which might occur when we try to take the fixed reservation at mount time... > > Hence I don't think that any algorithm that requires reading every > > AGF header in the filesystem at mount time on every v5 filesystem > > already out there in production (because finobt triggers this) is a > > particularly good idea... > > Perhaps not, but the horse bolted 5 years ago. :/ Let's go catch it :P Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx
