I am using s3ql on a vagrant vm (VirtualBox) CentOS 6.5 attaching to a swift cluster using keystone authentication. The vm did not unmount clean. I ran a fsck.s3ql on the storage url and it get;
Backend reports that file system is still mounted elsewhere. Either > the file system has not been unmounted cleanly or the data has not yet > propagated through the backend. In the later case, waiting for a while > should fix the problem, in the former case you should try to run fsck > on the computer where the file system has been mounted most recently. > Enter "continue" to use the outdated data anyway: I deleted the metadata out of the swift container and tried a remount, still getting the "File system damaged or not unmounted cleanly, run fsck!" Eventually I just dumped the container, the local cache and started over. Question is, is there a way to fix and preserve the data? I know this is an edge case with a testing vm. My goal here is to use this as a filesystem interface for multiple users hosted on a single production ready vm. -- 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.
