On Mar 09 2016, Nikolaus Rath <[email protected]> wrote:
> On Mar 09 2016, Cliff Stanford <[email protected]> wrote:
>> On 09/03/16 17:48, Nikolaus Rath wrote:
>>
>>> Are you using the right python-llfuse version (1.0)?
>>
>> I wasn't. I downloaded it and rebuilt and all the tests run
>> fine. However, after upgrading, I cannot write to the filesystem:
> [...]
>>
>> "/usr/local/lib/python3.4/dist-packages/s3ql-2.17-py3.4-linux-x86_64.egg/s3ql/inode_cache.py",
>> line 199, in create_inode
>> bindings)
>> File
>> "/usr/local/lib/python3.4/dist-packages/s3ql-2.17-py3.4-linux-x86_64.egg/s3ql/database.py",
>> line 104, in rowid
>> self.conn.cursor().execute(*a, **kw)
>> File "src/cursor.c", line 236, in resetcursor
>> apsw.ConstraintError: ConstraintError: NOT NULL constraint failed:
>> inodes.mtime
>
> Uh, it seems I have messed up the upgrade procedure. Please put the
> local metadata cache somewhere safe(tm). You need the .param and .db
> file, the -cache directory will hopefully be empty?
After backing up the metadata files, please try to run fsck.s3ql. After
that, please move the metadata files (now updated by fsck.s3ql)
somewhere else and try to run mount.s3ql. This should download metadata
from the backend (since there is no local copy). You should then be able
to create files again on the file system. Please also check the file
access times (e.g. using `stat <file>`). There was a possibility for
them to become corrupted (but I believe it did not happen in your case).
In a nutshell:
1. Backup metadata
2. fsck.s3ql
3. Move metadata out of the way
4. mount.s3ql
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.
