Even though i'm specifying the size, s3backer is autodetecting the size and complaining that the filesystem size and s3backer file size don't match and exits... so I can't run resize2fs as s3backer isn't running.
root@srvr:/var/log# s3backer --readOnly --blockSize=1024k --size=500g --listBlocks --vhost --ssl --timeout=250 --maxUploadSpeed=100k --blockCacheThreads=6 --blockCacheFile=/tmp/s3backerCache --accessFile=/etc/xxx --prefix=s3 srvr /s3
s3backer: auto-detecting block size and total file size...
s3backer: auto-detected block size=1m and total size=250g
s3backer: error: configured file size 500g != filesystem file size 250g
Then I did a bit of checking and spotted in s3b_config.c that s3backer will return a warning rather than an error if I include the --force flag.
So I tried again with
s3backer --force --blockSize=1024k --size=500g --listBlocks --vhost --ssl --timeout=250 --maxUploadSpeed=100k --blockCacheThreads=6 --blockCacheFile=/tmp/s3backerCache --accessFile=/etc/xxx --prefix=s3 srvr /s3
And I got further!
But before I could extend the filesystem with resize2fs I had to run:
e2fsck -f /s3/file
It took about 20 mins or so for it to complete recoverig the journal - I was getting worried! But after that it progressed with the passes quite nicely.
Once that was complete I could do
resize2fs -p /s3/file
and then remount the enlarged filesystem.
/dev/loop0 493G 226G 242G 49% /backups
/James