On Saturday, March 14, 2015 at 3:43:34 PM UTC-4, Nikolaus Rath wrote: > > On Mar 14 2015, Joseff Betancourt <[email protected] <javascript:>> > wrote: > > On Friday, March 13, 2015 at 9:05:03 PM UTC-4, Nikolaus Rath wrote: > >> On Mar 11 2015, Joseff Betancourt <[email protected] <javascript:>> > >> wrote: > >> > Seems I can't actually copy anything over now. I get an error in the > >> > mount.log as follows. Thanks for any help with this. > >> > > >> > File "/root/s3ql-2.12/src/s3ql/backends/swift.py", line 372, in > >> > open_read > >> > meta = self._extractmeta(resp, key) > >> > File "/root/s3ql-2.12/src/s3ql/backends/s3c.py", line 715, in _ > >> > extractmeta > >> > raise RuntimeError('Unknown metadata format: %s' % format_) > >> > RuntimeError: Unknown metadata format: raw2 > >> > >> This means that some of the data that's stored in the bucket was > written > >> with S3QL 2.13, so it's in format that S3QL 2.12 cannot understand. > This > >> is presumably because of the upgrade that you started but then > >> interrupted and tried to revert (I couldn't quite follow what exactly > >> you did). > >> > >> Are you certain this happens when you *write* a file though? E.g. when > >> you do "echo 'hello world' > /s3ql_mountpoint/a_new_file"? > >> > >> In any case, the easiest way to fix this is just to upgrade to S3QL > >> 2.13. > >> > > I'm trying to upgrade the files on rackspace as I cannot get them to > > even intiate in the local copy I downloaded. > > I don't know what you mean by this. > > > I just got to 33.2% of the upgrade and it died (repeated 3x). > > > > Error given is Backend does not have anything stored under key > > 's3ql_data_580910' > > > > full trace below: > [..] > > Traceback (most recent call last): > > File "/usr/lib/s3ql/s3ql/common.py", line 482, in run > > self.run_protected() > > File "/usr/lib/s3ql/s3ql/common.py", line 533, in run_protected > > self.target(*self.args, **self.kwargs) > > File "/usr/lib/s3ql/s3ql/adm.py", line 464, in upgrade_loop > > meta = plain_backend.lookup(obj_id) > > File "/usr/lib/s3ql/s3ql/backends/common.py", line 52, in wrapped > > return method(*a, **kw) > > File "/usr/lib/s3ql/s3ql/backends/swift.py", line 310, in lookup > > raise NoSuchObject(key) > > s3ql.backends.common.NoSuchObject: Backend does not have anything stored > > under key 's3ql_data_580910' > > S3QL believes it has stored something under this name, but the server > claims it is not there. This is probably a consequence of the aborted > first upgrade, or the subsequent crash. > > fsck.s3ql should be able to fix this - but it may run into other > unexpected problems. Have you tried runnnig the (S3QL 2.12) fsck? > > > I'm not sure what to do next as it seems I've exhausted all my options. > At > > this point I'm just trying to get a readonly mount so I can copy the > last > > two weeks of files. > > > > Is there a way I can sqladm upgrade from 2.12 to reset the version? > > I thought upgrading from 2.12 to 2.13 is exactly what you are trying to > do at the moment? (I don't know what you mean with resetting the version). > > 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.« >
Hi, I am trying to access the files that were placed unto the filesystem in the last X days (2 weeks). In an attempt to see if we could either access the files without the previous error when mounted and to try to limit the timeout errors in case we needed to upgrade I downloaded all 450GB to my hard drive locally with the idea to do a local://backend-folder, but this seems to not be able to do. With Local (2.12): - I cannot s3qladm download-metadata local://folder as it gives me a list of the backups but cannot get information for filename, skipping. Picking any number from the list results in an error. - I cannot fsck it as it errors about the database not being present. - I cannot mount as it tell s me to fsck it. - I cannot upgrade as it tells me it is a newer version (confused about partial upgrade of course). With Local (2.13): - I cannot s3qladm download-metadata. - I cannot s3qladm upgrade as it gives me an error. - I cannot fsck as it tells me to use 2.12 - I cannot mount as it says to fsck. Rackspace backend (2.12): - I cannot upgrade. - I can download metadata. - I can mount into list only. Cannot read/copy any object (what a tease here lol). Rackspace backend (2.13): - I can upgrade, but it would error at a specific file missing, which I may have fixed with a meta-download and feck (it deleted the spurious object :) - I can't mount. Again, I really am only looking for a temporary solution (2.12 OR 2.14 OR custom) to pull the files to move to a new raid solution for image hosting (we've given up on cloud hosting for files due to Rack Space's inconsistency since their hypervisor upgrades last week). -- 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.
