Re: BTRFS converted from EXT4 becomes read-only after reboot

2017-05-08 Thread Alexandru Guzu
to the root subvolume of a different disk. Is this possible? Thanks for the help and may this solution remain on the internet for anyone that has a similar issue. On Mon, May 8, 2017 at 3:02 PM, Sean Greenslade <s...@seangreenslade.com> wrote: > On Mon, May 08, 2017 at 02:22:52PM -0400, Alexa

Re: BTRFS converted from EXT4 becomes read-only after reboot

2017-05-08 Thread Alexandru Guzu
Getting a bit off-topic here, but were you able to boot from that fs with grub after a simple rsync? On Mon, May 8, 2017 at 1:01 PM, Sean Greenslade wrote: > On Mon, May 08, 2017 at 12:41:11PM -0400, Austin S. Hemmelgarn wrote: >> Send/receive is not likely to transfer

Re: BTRFS converted from EXT4 becomes read-only after reboot

2017-05-08 Thread Alexandru Guzu
-receive and then back work? On Sun, May 7, 2017 at 1:32 PM, Sean Greenslade <s...@seangreenslade.com> wrote: > On May 3, 2017 4:28:11 PM EDT, Alexandru Guzu <alexg...@gmail.com> wrote: >>Hi all, >> >>In a VirtualBox VM, I converted a EXT4 fs to BTRFS that is now runnin

BTRFS converted from EXT4 becomes read-only after reboot

2017-05-03 Thread Alexandru Guzu
Hi all, In a VirtualBox VM, I converted a EXT4 fs to BTRFS that is now running on Ubuntu 16.04 (Kernel 4.4.0-72). I was able to use the system for several weeks. I even did kernel updates, compression, deduplication without issues. Since today, a little while after booting (usually when I start

Re: Remounting read-write after error is not allowed

2017-04-18 Thread Alexandru Guzu
, or there is a strange bug in the kernel. I'll see if I can reproduce the issue again. On Mon, Apr 17, 2017 at 2:15 PM, Liu Bo <bo.li@oracle.com> wrote: > On Mon, Apr 17, 2017 at 02:00:45PM -0400, Alexandru Guzu wrote: >> Not sure if anyone is looking into that segfault, but I have

Re: Remounting read-write after error is not allowed

2017-04-17 Thread Alexandru Guzu
) Regards, On Fri, Apr 14, 2017 at 3:51 PM, Alexandru Guzu <alexg...@gmail.com> wrote: > Thanks for the reply. > > I mounted it ro: > $ sudo btrfs fi show /mnt > Segmentation fault (core dumped) > > dmesg says: > ... > kernel BUG at /build/linux-wXdoVv/

Re: Remounting read-write after error is not allowed

2017-04-14 Thread Alexandru Guzu
Thanks for the reply. I mounted it ro: $ sudo btrfs fi show /mnt Segmentation fault (core dumped) dmesg says: ... kernel BUG at /build/linux-wXdoVv/linux-4.4.0/fs/btrfs/ctree.c:5205! ... RIP: 0010:[] [] btrfs_search_forward+0x268/0x350 [btrfs] ... Call Trace: []

Remounting read-write after error is not allowed

2017-04-13 Thread Alexandru Guzu
Hello, I am not sure how to better summarize this but I'll give a more detailed description. I am using btrfs tools v4.4, I setup up a btrfs partition on an external USB2 drive and I started to play with it. The partition was about HALF full when I decided to run duperemove on it. This took a