From: Janpieter Sollie <janpieter.sollie@kabelmail.de>
To: linux-bcachefs@vger.kernel.org
Subject: debugging: how long do I need to keep data for other devs?
Date: Tue, 9 Feb 2021 10:51:07 +0100 [thread overview]
Message-ID: <cda37b74-eca0-4589-bc75-9e4bc7f181df@kabelmail.de> (raw)
Hi,
I am involved in 2 bcachefs bugs on github: #189 and #190.
Both errors make the data unreadable.
I have 3 bcachefs filesystems,
1 not moved to alloc_v2 and all devices present,
1 never moved to alloc_v2 but 1 foreground/promote device missing
1 moved to alloc_v2 and 1 foreground/promote device missing
Like any good IT guy, I create backups of my data.
but, for how long is it useful to keep the "broken" filesystem for repair? When can I simply
reformat the fs and revert to backup?
I know I could do it immediately - but this erases the faulty setup which needs to be examined
kind regards,
Janpieter
reply other threads:[~2021-02-09 10:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cda37b74-eca0-4589-bc75-9e4bc7f181df@kabelmail.de \
--to=janpieter.sollie@kabelmail.de \
--cc=linux-bcachefs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).