<alan@xxxxxxxxxxxxxxxxxxx> wrote:
Journals make the problem far worse.
Good to know and understand.
On restore you will restore a journal log no longer related to whats on
the media, then risk replaying it and causing further damage.
This makes sense. It was not clear to me that the journal was being stored in the "dump data". If so, can it be disabled immediately before dump(8) and then reenabled immediately after? Some highly volatile file systems (like the Oracle file-based database) claim to support hot backups. Assuming their marketing claim is actually valid, what would it take for the ext filesystem to support it?
Block reallocation is also nasty with a dump done that way because you
may end up with undetected data corruption including leaks of data
between uids.
With all these issues, it seems like 'man 8 dump' should advise against its use with mounted filesystems. The only mention of mount status is in the usage description, which indicates that mount points can only be used instead of block device names when calling dump when the filesystem is mounted.
A file system based backup is a good deal safer.
Isn't dump(8) considered a filesystem based backup? Are you refering to something more specialized?
Thanks.
--
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
