From: robin_listas@es.invalid   
      
   On 2024-05-02 11:37, J.O. Aho wrote:   
   > On 02/05/2024 07.52, Carlos E.R. wrote:   
   >> On 2024-04-30 15:33, J.O. Aho wrote:   
   >   
   >>> xfs_growfs will not change partition data, so if your 500GB /home was   
   >>> in a partition that was just 500GB then running the xfs_growfs will   
   >>> not do anything as there is nothing to do. If the partition was   
   >>> larger than the file system, then the command you run would add the   
   >>> rest of the partition to the file system.   
   >  >   
   >> There are some disadvantages for a grown xfs system compared to one   
   >> created with the big size from the start. I don't remember which, but   
   >> some of the structures do not cope very well (with large size grown).   
   >> I read about it in the xfs mail list.   
   >   
   > I doubt you will get this when grown from 500G to 2T, I could see issues   
   > when you go from 1T to 1P, but don't trust what I say too much as I'm   
   > far from an export on xfs, hardly used it myself, been more into jfs in   
   > the older days as xfs back then did be a big ram hog and was easily   
   > corrupted when abrupt "shutdowns".   
      
   I found a reference:   
      
       The problem was seen especially when the file system   
       was small initially and later grown to a larger size   
       using xfs_growfs. The log size does not grow when the   
       FS is grown. In these cases, we are stuck with the   
       same log size calculated for the smaller file system   
       size (which was 10MB, the earlier default value).   
      
      
   On new filesystem, the new default size is 64megs.   
      
   I don't know where the archive is for   
   X-Mailing-List: linux-xfs@vger.kernel.org   
   to point you to that thread.   
      
   --   
   Cheers, Carlos.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)