* Add big device, remove small device, now read-only
@ 2016-01-01 11:42 Rasmus Abrahamsen
0 siblings, 0 replies; only message in thread
From: Rasmus Abrahamsen @ 2016-01-01 11:42 UTC (permalink / raw)
To: linux-btrfs
Happy NY!
I have a raid with a 1TB, .5TB, 1.5TB and recently added a 4TB and want to remove the 1.5TB.
When saying btrfs dev delete it turned into readonly. I am on 4.2.5-1-ARCH and btrfs-progs v4.3.1 what can I do?
On top of that, my linux is on this same raid, so perhaps btrfs is writing some temp files in the filesystem but cannot?
. /dev/sdc1 on / type btrfs (ro,relatime,space_cache,subvolid=1187,subvol=/linux)
<zetok> Ralle: did you do balance before removing?
I did not, but I have experience with it balancing itself upon doing so.
Upon removing a device, that is.
I am just not sure how to proceed now that everything is read-only.
<zetok> I dunno, but generally with things that can crumble you should make it step-by-step
crumble?
<zetok> which, in combination arch + newest bleeding edge kernel should be mandatory
<zetok> I hope that you have backups?
I do have backups, but it's on Crashplan, so I would prefer not to have to go there.
<zetok> and do you have any logs?
Where would those be?
I never understood journalctl
<zetok> journalctl --since=today
Hmm, it was actually yesterday that I started the remove, so I did --since=yesterday
I am looking at the log now, please stnad by.
This is my log
http://pastebin.com/mCPi3y9r
But I fear that it became read-only before actually writing the error to the filesystem
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2016-01-01 11:42 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-01-01 11:42 Add big device, remove small device, now read-only Rasmus Abrahamsen
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).