This block device is a volume which is on hardware RAID. We have a few
machines like this running without issue. Something odd hit this one.
# free -m
total used free sharedbuffers cached
Mem: 32143 1258 30885 1 52
Am 10.08.2016 um 13:16 schrieb Matt McKinnon:
> I performed a quick balance which gave me:
>
> [39020.030638] BTRFS info (device sda1): relocating block group
> 25428383236096 flags 1
> [39020.206097] BTRFS warning (device sda1): block group 23113395863552
> has wrong amount of free space
>
Chris Murphy posted on Tue, 09 Aug 2016 20:25:39 -0600 as excerpted:
> 1 size 50.93TiB used 22.67TiB path /dev/sda1
>
> What is the exact nature of this block device?
>
> If getting this back up and running is urgent I suggest inquiring on IRC
> what the next steps are.
>
> In the meantime I'd
Hi,
from what i see you have a non finished balance ongoing, since you have
system and metadata DUP and single information on disk.
so you should (re)run a balance for this data.
sash
Am 10.08.2016 um 02:17 schrieb Matt McKinnon:
> -o usebackuproot worked well.
>
> after the file system
I performed a quick balance which gave me:
[39020.030638] BTRFS info (device sda1): relocating block group
25428383236096 flags 1
[39020.206097] BTRFS warning (device sda1): block group 23113395863552
has wrong amount of free space
[39020.206101] BTRFS warning (device sda1): failed to load
On Tue, Aug 9, 2016 at 6:29 PM, Matt McKinnon wrote:
> Spoke too soon. Do I need to continue to run with that mount option in
> place?
It shouldn't be necessary. Something's still wrong for some reason,
even with DUP metadata being CoW'd so someone else is going to have to
# btrfs check /dev/sda1
Checking filesystem on /dev/sda1
UUID: 33f9089e-acc7-4a39-8b83-b18bb182faaf
checking extents
ref mismatch on [958277767168 5894144] extent item 0, found 1
Backref 958277767168 root 257 owner 15799573 offset 750342144 num_refs 0
not found in extent tree
Incorrect local
] [] ret_from_fork+0x1f/0x40
[ 667.107056] [] ? kthread_park+0x60/0x60
[ 667.107060] ---[ end trace 336c80ba4db66e78 ]---
[ 667.107065] BTRFS: error (device sda1) in
btrfs_run_delayed_refs:2963: errno=-17 Object already exists
[ 667.116389] BTRFS info (device sda1): forced readonly
[ 667.117081] BTRFS
-o usebackuproot worked well.
after the file system settled, performing a sync and a clean umount, a
normal mount works now as well.
Anything I should be doing going forward?
Thanks,
Matt
On 08/09/2016 08:01 PM, Chris Murphy wrote:
On Tue, Aug 9, 2016 at 5:15 PM, Matt McKinnon
On Tue, Aug 9, 2016 at 6:01 PM, Chris Murphy wrote:
> On Tue, Aug 9, 2016 at 5:15 PM, Matt McKinnon wrote:
>> Hello,
>>
>> Our server recently crashed and was rebooted. When it returned our BTRFS
>> volume is mounting read-only:
>
> What happens
On Tue, Aug 9, 2016 at 5:15 PM, Matt McKinnon wrote:
> Hello,
>
> Our server recently crashed and was rebooted. When it returned our BTRFS
> volume is mounting read-only:
What happens when you try mounting with -o usebackuproot ?
If that fails, what output do you get for
Hello,
Our server recently crashed and was rebooted. When it returned our
BTRFS volume is mounting read-only:
[ 142.395093] BTRFS: error (device sda1) in
btrfs_run_delayed_refs:2963: errno=-17 Object already exists
[ 142.404418] BTRFS info (device sda1): forced readonly
I tried
12 matches
Mail list logo