You are not logged in.
Mar 30 18:52:19 Host sudo[2859]: nstgc : TTY=pts/0 ; PWD=/home/nstgc ; USER=root ; COMMAND=/usr/bin/btrfs balance start -dconvert=raid1 /btrfs/aroot
Mar 30 18:52:19 Host sudo[2859]: pam_unix(sudo:session): session opened for user root by (uid=0)
Mar 30 18:52:19 Host kernel: BTRFS info (device sdf4): relocating block group 188403941376 flags 65
Mar 30 18:52:54 Host kernel: BTRFS info (device sdf4): found 22940 extents
Mar 30 18:53:04 Host kernel: BTRFS info (device sdf4): found 22940 extents# uname -a
Linux Lain-BU 3.19.2-1-ARCH #1 SMP PREEMPT Wed Mar 18 16:21:02 CET 2015 x86_64 GNU/Linux# btrfs --version
btrfs-progs v3.19I started the conversion and the system locked up. I couldn't do anything. Sometimes when this happens I'm able to at least hit (as opposed to hold) the power buttom on my computer which initiates a power off. Instead I had to kill the power (hold the button down).I booted into my fall back installation checked the disks, ran a scrub, and finished the conversion.
Any clue what happened, or how I could find out other relevant information?
Offline
Best place for this is probably the btrfs development and user mailing list.
Offline
I think the issue is something other than btrfs. This time I was decrypting a test file. I don't know what caused it, but I know btrfs didn't like it. I now how a corrupt log tree it seems since I'm getting open_ctree failed errors in dmesg when trying to mount.
[edit] with a combination of btrfs-zero-log, mount -o recovery,degraded, scrub and check, my system seems to be back in action. This week end, however, I'm restoring from last week's back up. I'll wipe all partitions that make up the volume and and rsync from the oldest back up that still uses this same kernel.
Last edited by nstgc (2015-04-01 01:18:16)
Offline
I think the issue is something other than btrfs. This time I was decrypting a test file. I don't know what caused it, but I know btrfs didn't like it. I now how a corrupt log tree it seems since I'm getting open_ctree failed errors in dmesg when trying to mount.
Sounds like a case for btrfs-zero-log.
Best place for this is probably the btrfs development and user mailing list.
Additionally, #btrfs on freenode is a very welcoming place. Be patient for help though...
Offline
nstgc wrote:I think the issue is something other than btrfs. This time I was decrypting a test file. I don't know what caused it, but I know btrfs didn't like it. I now how a corrupt log tree it seems since I'm getting open_ctree failed errors in dmesg when trying to mount.
Sounds like a case for btrfs-zero-log.
davidm wrote:Best place for this is probably the btrfs development and user mailing list.
Additionally, #btrfs on freenode is a very welcoming place. Be patient for help though...
Yeah, it was a btrfs-zero-log issue. Or at least it became one. I think I may have some hardware issues. I have a Intel i7e with the CPU fan blowing hot on DiMMs. I think that may be the cause of the failure.
I've fixed it by the way
[edit]with a combination of btrfs-zero-log, mount -o recovery,degraded, scrub and check, my system seems to be back in action. This week end, however, I'm restoring from last week's back up. I'll wipe all partitions that make up the volume and and rsync from the oldest back up that still uses this same kernel.
Now I can get my old homework off my computer so I can finish up my mid term!
[edit] Next time something happens I probably will head over to the IRC. Given my track record that should be next Wednesday right before I meet with my thesis advisor next.
[edit2] Actually that bit about getting data off my computer was a cop-out. The volume effect was the, relatively, tiny one used for Arch. The one with with user generated data was fine. And my back ups are quite good.
Last edited by nstgc (2015-04-01 01:28:01)
Offline