Re: [s3ql] Recovering Deleted Files After rynsc --delete
On Sep 09 2020, "toffer...@gmail.com" wrote: > I use rysnc to sync some local files with a S3QL mount on DreamObjects. On > the last run of rsync, it deleted two files from my S3QL mount that I > assume had been deleted from the local drive due to filesystem errors on > the local drive. > > I am using S3QL and have not unmounted the S3QL filesystem since this > occurred. Although there are some empty folders in /.Trash-1000 folder on > the S3QL these deleted files are not. lost+found on the S3QL mount is also > empty. Yeah, these directories are only used by applications. I don't think rsync uses either of them. > Is there any way to recover the deleted files? Possibly in the local > cache? Nope, sorry. Best, -Nikolaus -- GPG 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 s3ql+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/s3ql/87sgbqbw7t.fsf%40vostro.rath.org.
[s3ql] Recovering Deleted Files After rynsc --delete
I use rysnc to sync some local files with a S3QL mount on DreamObjects. On the last run of rsync, it deleted two files from my S3QL mount that I assume had been deleted from the local drive due to filesystem errors on the local drive. I am using S3QL and have not unmounted the S3QL filesystem since this occurred. Although there are some empty folders in /.Trash-1000 folder on the S3QL these deleted files are not. lost+found on the S3QL mount is also empty. Is there any way to recover the deleted files? Possibly in the local cache? 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 s3ql+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/s3ql/711a-cbd6-4960-b099-6bc7bbacfdb2n%40googlegroups.com.
Re: [s3ql] BUG ALERT: Dirty inode was destroyed!
Hello Nicolas, > > S3QL somehow manages to delete/garbage collects an _Inode object > that is > dirty (i.e. has an attribute modification that is not persisted in > the > S3QL database) > > > So, if I understand correctly, since it is a pending modification on a > now deleted inode, this is not really a problem, right? Said > otherwise, the filesystem is not corrupted? [...] No, the inode/file does not have to be deleted. There is a pending metadata modification (access time, modification time, file size, file mode) that should have been persisted (written in the Sqlite-Database) but it did not made it in the database. File data is not corrupted, but some metadata of your files might not be in the correct state. -- 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 s3ql+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/s3ql/3d21a911-3ce2-7df4-0943-cff35d454075%40jagszent.de.
Re: [s3ql] BUG ALERT: Dirty inode was destroyed!
Hello! Sorry, it seems a previous answer did not go through. Thank you for your answer. > --> SQL 3.3.2 (I know, cannot upgrade right now) > You might want to first upgrade before diving into debugging this issue. > Since newer versions of S3QL use pyfuse3 instead of llfuse and also use > a newer trio versions it might very well be that your bug has vanished > in newer S3QL versions. Ok I did the upgrade to SQL 3.5.0 last week. --> The bug is still present (had one occurence in a week since the upgrade) --> BUT the filesystem no longer crash, which is good. S3QL somehow manages to delete/garbage collects an _Inode object that is > dirty (i.e. has an attribute modification that is not persisted in the > S3QL database) > So, if I understand correctly, since it is a pending modification on a now deleted inode, this is not really a problem, right? Said otherwise, the filesystem is not corrupted? If the filesystem is not corrupted, and it now no longer crashes, I can live with that :-) Thank you, Nicolas Deschildre -- 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 s3ql+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/s3ql/7e6316d6-4f07-4c56-a402-bd2f28bd9947n%40googlegroups.com.
