On Wed, Jul 24, 2024 at 10:44:47AM -0500, Eric Sandeen wrote: > On 7/24/24 10:41 AM, Eric Sandeen wrote: > > On 7/23/24 7:46 PM, Dave Chinner wrote: > >>> What about the log? If sb_agblocks increases, that can cause > >>> transaction reservations to increase, which also increases the minimum > >>> log size. > >> Not caring, because the current default minimum of 64MB is big enough for > >> any physical filesystem size. Further, 64MB is big enough for decent > >> metadata performance even on large filesystem, so we really don't > >> need to touch the journal here. <shrug> I think our support staff might disagree about that for the large machines they have to support, but log expansion doesn't need to be implemented in the initial proposal or programming effort. > > Seems fair, but just to stir the pot, "growing the log" offline, when > > you've just added potentially gigabytes of free space to an AG, should > > be trivial, right? Possibly -- if there's free space after the end and the log is clean. Maybe mkfs should try to allocate the log at the /end/ of the AG to make this easier? > Ugh I'm sorry, read to the end before responding, Eric. > > (I had assumed that an expand operation would require a clean log, but I > suppose it doesn't have to.) ...why not require a clean filesystem? Most of these 10000x XFS expansions are gold master cloud images coming from a vendor, which implies that we could hold them to slightly higher cleanliness levels. --D > -Eric > >
