Nikolaus Rath <[email protected]> writes:
> PA Nilsson <[email protected]> writes:
>>> It's a directory, not a file, and it is created when mount.s3ql
>>> starts. If this directory (with its contents) disappears if you reboot
>>> the system several minutes later, you have a real problem.
>>>
>> If I reboot several minutes later, the directory is there and everything
>> works. I need to force the reboot within seconds after the mount process,
>> or maybe even during it while the metadata is read/written from the
>> server.
>
> Ah, you didn't say that before. In that case there might be an easy
> fix that can be implemented in S3QL. Stay tuned, I'll send you a patch
> soonish.
Does the following patch fix the problem?
(This is for S3QL 2.8, let me know if you are using an earlier version).
diff --git a/src/s3ql/mount.py b/src/s3ql/mount.py
--- a/src/s3ql/mount.py
+++ b/src/s3ql/mount.py
@@ -432,6 +432,8 @@
backend['s3ql_seq_no_%d' % param['seq_no']] = b'Empty'
with open(cachepath + '.params', 'wb') as fh:
pickle.dump(param, fh, PICKLE_PROTOCOL)
+ fh.flush()
+ os.fsync(fh.fileno())
param['needs_fsck'] = False
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.
