[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1559723
As described in my previous comment, the fs was available in read-write
mode again.
I added another disk to the btrfs and with the additional space I was
able to rerun and successfully finish the btrfs balance operation (as
described in https://www.slicewise.net/debian/balancierung-eines-vollen-
I rebooted the system in the meantime. It now had Kernel 4.2.0-30.36
from previous updates:
cat /proc/version_signature
Ubuntu 4.2.0-30.36~14.04.1-generic 4.2.8-ckt3
During the reboot, the system performed some disk I/O for several hours.
Before services like sshd became available. I guess this
@jsalisbury
What exactly should I test on a broken file system with a newer Kernel?
How could this help you? If btrfs balance corrupted my file system, how
should a newer kernel fix that?
If you can tell me test a scenario which will help you to see if the bug
is fixed upstream, I'd be happy to
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.5 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix
Checking the underlying mdraid with
echo check > /sys/block/md0/md/sync_action
now has finished and it is just fine:
cat /proc/mdstat
Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] [raid4]
[raid10]
md0 : active raid1 sda3[0] sdb3[1]
2929833792 blocks super 1.2
Now, this one is funny after ~2 days:
# btrfs balance status x
Balance on 'x' is running
0 out of about 2797 chunks balanced (533 considered), 100% left
# btrfs balance cancel x
ERROR: balance cancel on 'x' failed - Read-only file system
So the balance is still running, consuming 100% of one
cat /proc/mounts
sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0
udev /dev devtmpfs rw,relatime,size=8157548k,nr_inodes=2039387,mode=755 0 0
devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0
tmpfs /run tmpfs
I found a few entries in kern.log, nothing special during btrfs balance:
Mar 19 03:47:03 server kernel: [2970569.341605] BTRFS info (device dm-0):
relocating block group 9553211031552 flags 36
Mar 19 04:01:08 server kernel: [2971415.588391] BTRFS info (device dm-0):
relocating block group
Error messages in dmesg |tail are still ongoing, presumably originating
from the btrfs command which still is eating 100% of the cpu,
I did not reboot yet nor kill the btrfs process (pid 27516).
Here's two lines from two of the latest error messages in dmesg:
[3111643.576434] []
Something noticable: The command btrfs is consuming 100% of the cpu for
a long time:
# top
[...]
PID BENUTZER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND
27516 root 20 0 15476132 0 R 100,0 0,0 1348:33 btrfs
I assume that this process originates from my
Currently, I'm checking the md-raid (raid 1) with
echo check > /sys/block/md0/md/sync_action
I have 2 x 3.5TB hard drives, so this will take some while.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The underlying md-raid (mirroring) is fine. So according to md-raid
status, there's nothing wrong with the mirrored partitions:
cat /proc/mdstat
Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] [raid4]
[raid10]
md0 : active raid1 sda3[0] sdb3[1]
2929833792 blocks
Some relevant lines from /var/log/syslog:
Mar 19 19:15:10 server smartd[2251]: Device: /dev/sdb [SAT], SMART Usage
Attribute: 194 Temperature_Celsius changed from 107 to 106
Mar 19 07:59:21 server console-kit-daemon[2041]: GLib-CRITICAL: Source ID 376
was not found when attempting to remove it
related: https://www.mail-archive.com/linux-
bt...@vger.kernel.org/msg48609.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1559723
Title:
soft lockup during btrfs balance
To manage
I have # btrfs --version
Btrfs v3.12
Kernel is from Hardware enablement stack 14.04.4, Btrfs-tools from
ubuntu's package respectively.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1559723
Title:
# apt-cache policy btrfs-tools
btrfs-tools:
Installiert: 3.12-1ubuntu0.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1559723
Title:
soft lockup during btrfs balance
To manage
Related: https://www.spinics.net/lists/linux-btrfs/msg48037.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1559723
Title:
soft lockup during btrfs balance
To manage notifications about this
Related: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1349711
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1559723
Title:
soft lockup during btrfs balance
To manage notifications about
For my setup, btrfs file system runs on top of a LUKS encrypted
partition which itself is on top of a mdraid (mirroring).
The Layout is:
# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:00 2,7T 0 disk
├─sda1 8:10
** Attachment added: "uname-a.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1559723/+attachment/4605660/+files/uname-a.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1559723
Title:
** Attachment added: "lspci-vvnn.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1559723/+attachment/4605659/+files/lspci-vvnn.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1559723
Note that some months ago (when I got the error message), I still was
able to cleanly free up some diskspace and perform a clean btrfs balance
(which freed a lot of space).
My hope was that I'd get an error message and exit cleanly if disk space
is missing. Instead, I got the soft lockup.
--
related: #1349711
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1559723
Title:
soft lockup during btrfs balance
To manage notifications about this bug go to:
24 matches
Mail list logo
