mount log: 2014-06-18 13:07:05.469 [3893] MainThread: [mount] Using 4 upload threads. 2014-06-18 13:07:06.476 [3893] MainThread: [mount] Ignoring locally cached metadata (outdated). 2014-06-18 13:07:06.667 [3893] MainThread: [root] Backend reports that fs is still mounted elsewhere, aborting.
fsck.s3ql s3://xxxxx/ Ignoring locally cached metadata (outdated). 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: But if I type continue it downloads what seems to be an out of date metadata? (it's 48Mb the local backup is 178Mb) When I run s3qladm download-metadata s3://xxxxx it shows me bak files from 1 year ago :( here is the log before I killed the process. fsck.log 2014-06-18 13:09:33.264 [4039] MainThread: [fsck] Ignoring locally cached metadata (outdated). 2014-06-18 13:09:49.719 [4039] MainThread: [fsck] Downloading and decompressing metadata... 2014-06-18 13:09:52.733 [4039] MainThread: [fsck] Reading metadata... 2014-06-18 13:09:52.735 [4039] MainThread: [metadata] ..objects.. 2014-06-18 13:09:55.099 [4039] MainThread: [metadata] ..blocks.. 2014-06-18 13:09:58.414 [4039] MainThread: [metadata] ..inodes.. 2014-06-18 13:10:01.647 [4039] MainThread: [metadata] ..inode_blocks.. 2014-06-18 13:10:04.515 [4039] MainThread: [metadata] ..symlink_targets.. 2014-06-18 13:10:04.516 [4039] MainThread: [metadata] ..names.. 2014-06-18 13:10:05.774 [4039] MainThread: [metadata] ..contents.. 2014-06-18 13:10:09.780 [4039] MainThread: [metadata] ..ext_attributes.. 2014-06-18 13:10:11.354 [4039] MainThread: [fsck] Creating temporary extra indices... 2014-06-18 13:10:12.770 [4039] MainThread: [fsck] Checking lost+found... 2014-06-18 13:10:12.771 [4039] MainThread: [fsck] Checking cached objects... On Wednesday, 18 June 2014 18:58:53 UTC+7, Warren Daly wrote: > > Ok I have a backup of the local metadata - the one I was using is 48Mb, > but the one I have from backup is 178Mb (.db) file. > So I probably did lose those objects that fsck deleted ([fsck] Deleted > spurious object) > > So I placed the backup of the .db and params file in the .s3ql folder. > > When I run: > mount.s3ql --allow-other s3:/xxxx/ /folder/ > I see this in the mount.log file: > 2014-06-18 12:52:07.928 [2980] MainThread: [mount] Using 4 upload threads. > 2014-06-18 12:52:08.669 [2980] MainThread: [mount] Ignoring locally cached > metadata (outdated). > 2014-06-18 12:52:08.772 [2980] MainThread: [root] Backend reports that fs > is still mounted elsewhere, aborting. > > I know there is nothing else mounting, because I've just booted the > instance. Investigating now. > Also reading up on how to not ignore local metadata? > > Thanks, > Warren > > On Wednesday, 18 June 2014 14:31:14 UTC+7, Warren Daly wrote: >> >> Dear Nikoluas, >> thank you for your time and effort to reply. I really appreciate you >> help. Thank you. >> >> A general question, under normal operations, What does fsck mean when it >> says "[fsck] Deleted spurious object" >> is it removing items on the S3 drive that are no longer in the local >> metadata file? >> >> I thought that the mount would always use the local metadata when running >> "mount.s3ql --allow-other s3://xxxx/ /folder/" >> >> I will obtain the all the logs and send them in the next email. >> >> Thanks again, >> Warren >> >> >> On Wednesday, 18 June 2014 03:19:12 UTC+7, Nikolaus Rath wrote: >>> >>> Warren Daly <[email protected]> writes: >>> > I use Ubuntu 12.04 LTS 64 bit server. >>> > Running python 2.7 so running s3ql-1.12 >>> > <http://code.google.com/p/s3ql/downloads/detail?name=s3ql-1.17.tar.bz2> >>> >>> >>> Aeh, which one now? 1.12 or 1.17/ >>> >>> > I mount an S3 bucket using mount.s3ql All has been working fine for >>> > quite sometime. I need to perform some security updates on the server. >>> > So I unmounted the S3 bucket. Rebooted the server. >>> > >>> > When I try to mount the S3 bucket: >>> > mount.s3ql --allow-other s3://xxxx/ /production/ >>> > It returns: >>> > File system damaged or not unmounted cleanly, run fsck! >>> > >>> > So I run fsck.s3ql..... >>> > .... >>> > MainThread: [fsck] ..processed 605000 objects so far.. >>> > MainThread: [fsck] Deleted spurious object 181363 >>> > MainThread: [fsck] Deleted spurious object 181364 >>> > MainThread: [fsck] Deleted spurious object 181365 >>> > MainThread: [fsck] Deleted spurious object 181366 >>> > MainThread: [fsck] Deleted spurious object 181367 >>> > MainThread: [fsck] Deleted spurious object 181368 >>> > MainThread: [fsck] Deleted spurious object 181369 >>> > MainThread: [fsck] Deleted spurious object 181370 >>> > MainThread: [fsck] Deleted spurious object 181371 >>> > MainThread: [fsck] Deleted spurious object 181372 >>> > >>> > It's starts counting upwards from object 181363 saying Deleted >>> spurious >>> > object. So I killed the process. >>> > >>> > *Is it safe to continue to run fsck and have it Deleted spurious >>> > objects? * >>> >>> If the metadata is correct, yes. But that may not be the case for you. >>> >>> > Is there a switch (I cannot find on in the man file, or help) to move >>> to >>> > lost&found or not to delete. >>> >>> No, but I could create a quick patch if necessary. >>> >>> > Please help. Any assistance appreciated. >>> > >>> > When I run s3qladm download-metadata s3://xxxxx >>> > I see this: >>> > >>> > No Name Date >>> > 0 s3ql_metadata_bak_0 2013-07-02 11:14:55 >>> > 1 s3ql_metadata_bak_1 2013-07-01 11:14:14 >>> > 2 s3ql_metadata_bak_10 2013-06-24 03:34:58 >>> > 3 s3ql_metadata_bak_2 2013-07-01 03:20:06 >>> > 4 s3ql_metadata_bak_3 2013-06-30 03:19:49 >>> > 5 s3ql_metadata_bak_4 2013-06-29 03:13:52 >>> > 6 s3ql_metadata_bak_5 2013-06-28 14:08:21 >>> > 7 s3ql_metadata_bak_6 2013-06-28 03:36:40 >>> > 8 s3ql_metadata_bak_7 2013-06-27 03:36:20 >>> > 9 s3ql_metadata_bak_8 2013-06-26 03:35:40 >>> > 10 s3ql_metadata_bak_9 2013-06-25 03:35:20 >>> > >>> > *Why are the backups so old? Surely metadata refreshes at the default >>> (24 >>> > hour) periods? * >>> >>> It should, unless you pass a different option. What does your >>> ~/.s3ql/mount.log file say? It should report whenever metadata is saved. >>> >>> > So these will be pretty useless to me. But I have local metadata. The >>> > server didn't crash was shutdown and restarted just fine. >>> > >>> > I have the the .db file and params file. I understand that fsck will >>> use >>> > this local metadata. >>> >>> Did it say so? You unfortunately didn't include the full fsck.s3ql >>> output. >>> >>> >>> 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.« >>> >> -- 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.
