From: Sanidhya Solanki <lkml.page@gmail.com>
To: Alexandru Guzu <alexguzu@gmail.com>
Cc: Sean Greenslade <sean@seangreenslade.com>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>,
Qu Wenruo <quwenruo@cn.fujitsu.com>
Subject: Re: BTRFS converted from EXT4 becomes read-only after reboot
Date: Mon, 8 May 2017 11:28:42 -0400 [thread overview]
Message-ID: <20170508112617.7e33bed6@ad> (raw)
In-Reply-To: <CAPktuGuyUBQF1=LKvmpZiS7vMSsu=LCfqA9PFa7ObK9ih=LoXg@mail.gmail.com>
On Mon, 8 May 2017 10:16:44 -0400
Alexandru Guzu <alexguzu@gmail.com> wrote:
> Sean, how would you approach the copy of the data back and forth if
> the OS is on it? Would a Send-receive and then back work?
You could use a Live-USB and then just dd it to remote or attached storage, if
you want to be absolutely sure the data is not affected.
SS
next prev parent reply other threads:[~2017-05-08 15:28 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-03 20:28 BTRFS converted from EXT4 becomes read-only after reboot Alexandru Guzu
2017-05-03 22:18 ` Chris Murphy
2017-05-04 3:55 ` Duncan
2017-05-23 17:00 ` Marc MERLIN
2017-05-23 21:38 ` Chris Murphy
2017-05-23 21:49 ` Marc MERLIN
2017-05-23 21:51 ` Chris Murphy
2017-05-23 21:53 ` Marc MERLIN
2017-05-23 22:02 ` Marc MERLIN
2017-05-23 21:51 ` Hugo Mills
2017-05-24 4:03 ` Andrei Borzenkov
[not found] ` <CAPktuGtqt-tVNvbxkdaEB7PshWVpDHsxfHYMujOkAvOP9aiJ6w@mail.gmail.com>
2017-05-05 15:40 ` Chris Murphy
[not found] ` <CAPktuGtTVMFcrh1QRgnXXiS9HvrKDEYK9kAumUGToY+ycaMoCA@mail.gmail.com>
2017-05-05 21:26 ` Chris Murphy
2017-05-07 17:32 ` Sean Greenslade
2017-05-08 14:16 ` Alexandru Guzu
2017-05-08 15:28 ` Sanidhya Solanki [this message]
2017-05-08 16:22 ` Sean Greenslade
2017-05-08 16:41 ` Austin S. Hemmelgarn
2017-05-08 17:01 ` Sean Greenslade
2017-05-08 18:22 ` Alexandru Guzu
2017-05-08 19:02 ` Sean Greenslade
2017-05-08 19:15 ` Alexandru Guzu
2017-05-08 19:30 ` Chris Murphy
2017-05-08 19:09 ` Chris Murphy
2017-05-08 19:05 ` Chris Murphy
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=20170508112617.7e33bed6@ad \
--to=lkml.page@gmail.com \
--cc=alexguzu@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo@cn.fujitsu.com \
--cc=sean@seangreenslade.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.