btrfsck crashed with SIGABRT in __assert_fail_base()

Bug #930428 reported by Arnulf Heimsbakk on 2012-02-10
36
This bug affects 5 people
Affects Status Importance Assigned to Milestone
btrfs-tools (Ubuntu)
Medium
Unassigned

Bug Description

Precise comes with old btrfs-tools. Don't have new features supported by the kernel module as the new compression lzo.

btrfsck crashed here on a volume mounted with compress=lzo.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: btrfs-tools 0.19+20100601-3ubuntu3
ProcVersionSignature: Ubuntu 3.2.0-8.15-generic 3.2.0
Uname: Linux 3.2.0-8-generic x86_64
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
Date: Fri Feb 10 21:56:32 2012
ExecutablePath: /sbin/btrfsck
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120112)
ProcCmdline: btrfsck /dev/sda3
Signal: 6
SourcePackage: btrfs-tools
StacktraceTop:
 raise () from /lib/x86_64-linux-gnu/libc.so.6
 abort () from /lib/x86_64-linux-gnu/libc.so.6
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 __assert_fail () from /lib/x86_64-linux-gnu/libc.so.6
 ?? ()
Title: btrfsck crashed with SIGABRT in raise()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

visibility: private → public

StacktraceTop:
 __assert_fail_base (fmt=<optimized out>, assertion=0x4173ae "!(1)", file=0x41833c "disk-io.c", line=<optimized out>, function=<optimized out>) at assert.c:94
 __GI___assert_fail (assertion=0x4173ae "!(1)", file=0x41833c "disk-io.c", line=679, function=0x4186a8 "open_ctree_fd") at assert.c:103
 open_ctree_fd (fp=3, path=0x7fff6714d885 "/dev/sda3", sb_bytenr=<optimized out>, writes=<optimized out>) at disk-io.c:659
 open_ctree (filename=0x7fff6714d885 "/dev/sda3", sb_bytenr=0, writes=0) at disk-io.c:583
 main (ac=<optimized out>, av=<optimized out>) at btrfsck.c:2835

Changed in btrfs-tools (Ubuntu):
importance: Undecided → Medium
summary: - btrfsck crashed with SIGABRT in raise()
+ btrfsck crashed with SIGABRT in __assert_fail_base()
tags: removed: need-amd64-retrace
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in btrfs-tools (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers