Update:
fixing the NFS mount was only doable by restarting the NFS service, the
/mnt/local-nfs became accessible, but mount.s3ql did not reconnect
(automatically?). So I killed the mount.s3ql, and ran fsck.s3ql against the
NFS storage backend, took a while, committed lots of cached stuff, but
stopped on this:
Checking directory reachability...
Checking unix conventions...
Checking referential integrity...
Dropping temporary indices...
Dumping metadata...
..objects..
..blocks..
Uncaught top-level exception:
Traceback (most recent call last):
File "/bin/fsck.s3ql", line 9, in <module>
load_entry_point('s3ql==2.9', 'console_scripts', 'fsck.s3ql')()
File "/usr/lib/python3.3/site-packages/s3ql/fsck.py", line 1217, in main
dump_metadata(db, fh)
File "/usr/lib/python3.3/site-packages/s3ql/metadata.py", line 137, in
dump_metadata
dump_table(table, order, columns, db=db, fh=fh)
File "deltadump.pyx", line 317, in s3ql.deltadump.dump_table
(src/s3ql/deltadump.c:4096)
File "deltadump.pyx", line 364, in s3ql.deltadump.dump_table
(src/s3ql/deltadump.c:3746)
ValueError: Can't dump NULL values
Mounting is not possible:
[root@strobiserver ~]# mount.s3ql local:///mnt/local-nfs/myfsdata-ttt
/mnt/s3ql-ttt-local --allow-other --nfs
Using 4 upload threads.
Autodetected 4052 file descriptors available for cache entries
Enter file system encryption passphrase:
Using cached metadata.
File system damaged or not unmounted cleanly, run fsck!
Rerunning fsck gives same output as above.
Suggestions to get out of this?
Thank you!
--
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.
