Hi Sven, 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!
Sven Martin <[email protected]> writes: > Hi Nikolaus, > > The server I mounted a S3QL file system on is still in test. I installed > owncloud and configured its data directory to be on a mounted S3 volume > using S3QL. Rebooting automounts the volume. I was on holiday for a week > and when I came back the system had no free disk space. It turned out the > volume was not mounted and the mountpoint got filled up with owncloud data. > I don't knwo what caused the volume to unmount. I deleted the data (user > data, but it's test so no issue) to free up space, rebooted the server. Now > I am unable to mount the S3 filesystem. It keeps saying "Mounting > filesystem..." and does not return to the prompt. Running fsck.s3ql --force > works but does not help. > > Any tips & tricks? What S3QL version are you using? Note the following entries in the Changelog: 2014-09-04, S3QL 2.11.1 * By popular demand, mount.s3ql is now able to daemonize again and also does so by default. 2014-08-27, S3QL 2.11 * mount.s3ql no longer daemonizes on its own. With a modern init system this should no longer be necessary, and when running mount.s3ql from the command line the shell can be used to put the process into background. Best, Nikolaus PS: Please remember the first paragraph when replying. -- GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F »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.
