Replies: 3 comments 4 replies
|
I have tried adding the max-space parameter to fstab, but it does not help: avtech-juice-vol01 /fileserver1 juicefs _netdev,allow_other,max-space=10000 0 0 |
0 replies
|
could you please share the version of JuiceFS you are using? |
2 replies
|
before: mjc@avtechpulse.com volume: avtech-juice-vol01 |
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hi,
I moved an AWS-S3-based volume between juicefs accounts (i.e., transfered ownership on the juicefs side).
There were no changes on the AWS end.
juicefs now reports a disk size of 1TB ("Capacity 1 TiB space, 1 M inodes (files and directories)"), and zero free space - but I can in practice add more data. The problem is certain utilities check for free space and are very unhappy if the filesystem says zero.
Before the ownership transfer, juicefs reported a disk size of 1 or 10 PB (I forget which), and thus lots of free space was reported.
How can I get back to the previous setup with a non-zero reported free space?
All reactions