On Thursday, December 17, 2015 at 11:03:54 AM UTC-5, Nikolaus Rath wrote: > > On Dec 17 2015, Jamie Fargen <[email protected] <javascript:>> wrote: > > I noticed that an s3ql file system was down and when I tried to mount it > > the mount failed and the error stated that s3ql.fsck needed to be > executed. > > While running the fsck many messages like Deleted spurious object > 245444, > > were received. > > > > This is the final output of the fsck: > > Deleted spurious object 245442 > > Deleted spurious object 245443 > > Deleted spurious object 245444 > [...] > > > > After the fsck finished I remounted the file system and all the files > are > > now missing. > > > > Looking at the object container it had 2T of data before the fsck and > now > > only has a few megabytes. > > Sounds like the mount crashed before any metadata was uploaded, and you > then ran fsck.s3ql with a different --cachedir (or you also lost the > cache directory, or you ran it on a different computer). > > > Best, > -Nikolaus > > -- >
> 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.« > On Thursday, December 17, 2015 at 11:03:54 AM UTC-5, Nikolaus Rath wrote: > > On Dec 17 2015, Jamie Fargen <[email protected] <javascript:>> wrote: > > I noticed that an s3ql file system was down and when I tried to mount it > > the mount failed and the error stated that s3ql.fsck needed to be > executed. > > While running the fsck many messages like Deleted spurious object > 245444, > > were received. > > > > This is the final output of the fsck: > > Deleted spurious object 245442 > > Deleted spurious object 245443 > > Deleted spurious object 245444 > [...] > > > > After the fsck finished I remounted the file system and all the files > are > > now missing. > > > > Looking at the object container it had 2T of data before the fsck and > now > > only has a few megabytes. > > Sounds like the mount crashed before any metadata was uploaded, and you > then ran fsck.s3ql with a different --cachedir (or you also lost the > cache directory, or you ran it on a different computer). > > > Best, > -Nikolaus > > -- > 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.« > On Thursday, December 17, 2015 at 11:03:54 AM UTC-5, Nikolaus Rath wrote: > > On Dec 17 2015, Jamie Fargen <[email protected] <javascript:>> wrote: > > I noticed that an s3ql file system was down and when I tried to mount it > > the mount failed and the error stated that s3ql.fsck needed to be > executed. > > While running the fsck many messages like Deleted spurious object > 245444, > > were received. > > > > This is the final output of the fsck: > > Deleted spurious object 245442 > > Deleted spurious object 245443 > > Deleted spurious object 245444 > [...] > > > > After the fsck finished I remounted the file system and all the files > are > > now missing. > > > > Looking at the object container it had 2T of data before the fsck and > now > > only has a few megabytes. > > Sounds like the mount crashed before any metadata was uploaded, and you > then ran fsck.s3ql with a different --cachedir (or you also lost the > cache directory, or you ran it on a different computer). > > > Best, > -Nikolaus > > -- > 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.« > How can one improve metadata consistency and ensure that it is uploaded regularly? Why isn't metadata atomic? When I mount the volume I do specify a --cachedir, but when I ran fsck I did not specify the cachedir. The cachedir only has about 7.5GB of data vs 2TB of data lost. Why would missing cached data result in losing 100% of the file system? The file system was mounted from the same computer. -- 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.
