Hi PA, When replying to emails on this list, please do not put your reply above the quoted text, and do not quote the entire message you're answering to. This makes it unnecessarily hard for other readers to understand the context of your email. Instead, please cut quoted parts that are not relevant to your reply, and insert your responses right after the points you're replying to (as I have done below). Thanks!
PA Nilsson <[email protected]> writes: > A follow up question on this. > > When mounting a file system using an s3c backend, running 'df' will > report that the filsystem has 1TB size. There is no such information > coming from the backend, but is is easily made available. > > Can information on this somehow be propagated? As far as I know, there is no such information from most backends. Google Storage, Amazon S3, OpenStack et al all have effectively unlimited storage. I believe only the local backend could effectively report a capacity. Which backend do you have in mind? But even if we got a number from the backend, it's not clear what we should report to df. How do we take into account compression and deduplication? Best, -Nikolaus -- Encrypted emails preferred. PGP fingerprint: 5B93 61F8 4EA2 E279 ABF6 02CF A9AD B7F8 AE4E 425C »Time flies like an arrow, fruit flies like a Banana.« -- You received this message because you are subscribed to the Google Groups "s3ql" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
