similar to: Recovering data from old corrupted file system

Hi, I''m running OpenSuse 12.2 with kernel 3.5.3 HBA= LSI 1068e using the MPTSAS driver (patched) (https://patchwork.kernel.org/patch/1379181/) SANOS1:/media # uname -a Linux SANOS1 3.5.3 #3 SMP Sun Sep 2 18:44:37 CEST 2012 x86_64 x86_64 x86_64 GNU/Linux I''ve tried to simulate a disk replacement but it seems that now /dev/sdg is stuck in the btrfs pool (RAID10) SANOS1:/media #

Hello Developers, it seems that i discovered a bug in btrfs while testing it on a zSeries mainframe :-) ## Test environment: - IBM System z900 Mainframe - Debian SID with 64 Bit Kernel - GIT Sources from git://git.kernel.org/pub/scm/linux/kernel/git/mason/btrfs-unstable.git - System runs as z/VM guest - 3 Virtual CPUs - 1 GB RAM Storage ## Initial Test Setup - Setup a Debian SID System with

I booted the guest in which i was testing btrfs (transient ENOSPC issues, etc). It booted in emergency mode. [ 6.705187] device label testfs1 devid 1 transid 4141 /dev/sdb1 [ 6.724353] device label fedora devid 1 transid 2036 /dev/sda2 [ 6.780931] device label fedora devid 1 transid 2036 /dev/sda2 [ 6.817157] snd_hda_intel 0000:00:04.0: irq 42 for MSI/MSI-X [ 6.818326]

Hey, I''d start by saying that I know Btrfs is a still experimental, and so there''s no guarantee that one would be able to help me at all... But I thought I''ll try anyway :-) Few months ago I bought a new laptop and installed ArchLinux on it, with Btrfs on the root filesystem... I know, it''s not the smartest thing to do... After a few month I had issues with my

Hello, I had a raid1 btrfs (540GB) on vanilla 3.6.3, a disk failed, and removed it at power off, plugged in a new one, partitioned it (to 110GB, by error), and added it to btrfs. I tried to remove the missing device, and it said "Input/output error" after a while. Next attempts simply gave "Invalid argument". I repartitioned, rebooted the system, and made the partition grow:

On Mon, Sep 07, 2020 at 09:14:03PM +0200, Karol Herbst wrote: > > - changes in the nouveau driver. Mika told me the PCIe regression > > "pcieport 0000:00:01.0: PME: Spurious native interrupt!" is supposed > > to be fixed in 5.8, but I still get a 4mn hang or so during boot and > > with 5.8, removing the USB key, didn't help make the boot faster >

I created a 1TB RAID1. So far it is just for testing, no important data on there. After a reboot, I tried to mount it again # mount /dev/mapper/vg00-btrfsvol0_0 /mnt/btrfs0 mount: wrong fs type, bad option, bad superblock on /dev/mapper/vg00-btrfsvol0_0, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or

Hi! The problem is that the BTRFS raid10 filesystem without any understandable cause refuses to mount. Here is dmesg output: [77847.845540] device label linux-btrfs-raid10 devid 3 transid 45639 /dev/sdc1 [77848.633912] btrfs: allowing degraded mounts [77848.633917] btrfs: enabling auto defrag [77848.633919] btrfs: use lzo compression [77848.633922] btrfs: turning on flush-on-commit [77848.658879]

Hi, I have a home server on Linux Arch (kernel 3.11.2) that uses multi-device btrfs on root filesystem. Until recently it worked completely fine. And yesterday I rebooted it and the machine did not wake up. I booted from a USB (kernel 3.10) and tried to mount the filesystem. Here is OOPs I see [ 41.676217] device fsid 25e6a6fa-fe1f-4be5-a638-eeac948f8c21 devid 8 transid 164237 /dev/sda [

Hello, trying out btrfs on my linux installation. I am running Funtoo with Linux 3.0 kernel. After a reboot kernel panicked (no access to error log since it is my root volume that failed). I get this using a rescue cd (2.6.38, btrfs v 0.19) and then trying to mount : [  752.129118] btrfs bad tree block start 0 131072 [  752.129152] btrfs: failed to read chunk root on sda5 [  752.132190] btrfs:

I've just tried putting usr in a subvol. Installation proceeds normally, no errors, but I'm dropped to a dracut prompt which indicates mount of /usr failed. dmesg follows: [ 14.025215] systemd[1]: Starting dracut initqueue hook... [ 14.077890] Btrfs loaded [ 14.129987] device label fedora_f18v devid 1 transid 31 /dev/sda1 [ 14.313607] device label fedora_f18v devid 1 transid 31

Hello! Today I downgraded from Ubuntu''s APT repo "oneiric-proposed" (which brings some kernel 3.0.0-13) back to the standard repo "oneiric". Now I''m not able to mount my btrfs / and /home (both on the same partition) anymore: device fsid SOME-UUID devid 1 transid 84229 /dev/dm-0 parent transid verify failed on 77078528 wanted 83774 found 84226

Hi, the $subj warning appears sometimes in syslog, in my case when xfstests/209 runs looped. The minimal reproducer is looped mkfs+mount. The message comes from disk-io.c btree_readpage_end_io_hook(): 581 if (check_tree_block_fsid(root, eb)) { 582 printk_ratelimited(KERN_INFO "btrfs bad fsid on block %llu\n", 583 (unsigned long

Btrfs has been broken for me for ages. I first reported it on this list 5 months ago[1]. Below is a very simple reproducer that anyone can run. *NB* before you run this, adjust /dev/sda & /dev/sda1 to point to an unused block device! ---------------------------------------------------------------------- #!/bin/sh - set -e while true; do parted -s -- /dev/sda mklabel msdos parted -s --

Hi folks! Been using btrfs for quite a while now, worked great until now. Got power-loss on my machine and now i have the "parent transid verify failed on X wanted X found X" problem. So I can''t get it to mount. My btrfs is spread over sda (2tb), sdc(2tb), sdd(1tb). Is this something that an offline fsck could fix ? If so is the fsck-util being developed ? Is there a way to

So I''m having a bit of trouble with one of my btrfs filesystems. It isn''t mounting after a power failure. I can''t get restore or btrfsck to run, even on backup supers. I''ve pasted some output below. My btrfs-progs below come from git this morning, running on linux 3.2.0. # mount /dev/md2 /media/test/ mount: wrong fs type, bad option, bad superblock on

Hello I did the following commands and resulted in a segmentation fault. [root@localhost ~]# mkfs.btrfs /dev/sda6 WARNING! - Btrfs Btrfs v0.19 IS EXPERIMENTAL WARNING! - see http://btrfs.wiki.kernel.org before using fs created label (null) on /dev/sda6 nodesize 4096 leafsize 4096 sectorsize 4096 size 46.93GB Btrfs Btrfs v0.19 [root@localhost ~]# mount /dev/sda6 /mnt/btra [root@localhost ~]#

Hallo, I''d like to get some explanations ... # btrfs filesystem show Label: ''MMedia'' uuid: 120b036a-883f-46aa-bd9a-cb6a1897c8d2 Total devices 3 FS bytes used 3.80TB devid 1 size 1.82TB used 1.29TB path /dev/sdg1 devid 3 size 1.81TB used 1.29TB path /dev/sdc1 devid 2 size 1.81TB used 1.28TB path /dev/sdb1 Btrfs Btrfs v0.19 # btrfs filesystem df /srv/MM

Hi all, I am using a single volume across two devices sdb7 and sda1, initially created on sdb7, and added sda1 using btrfs-vol later. The fstab entry: /dev/disk/by-id/scsi-SATA_ST31000333AS_9TE12DSC-part7 /mnt/btrfs btrfs defaults 1 2 Now after boot I get: ---- device fsid c4822885057410c-d2d65a83c2f15fb4 devid 1 transid 73034 /dev/sdb7 btrfs: failed to read chunk tree on sdb7 ---- So I have

Hello, I have noticed I have the following in my dmesg: [319769.043163] nbd: registered device at major 43 [319769.104176] nbd11: unknown partition table [319769.130273] device fsid c2598ff2-1e3e-4edf-ab19-1f7ab41b0160 devid 1 transid 125743 /dev/nbd11 [319769.130522] btrfs: force lzo compression [319769.130528] btrfs: disk space caching is enabled [319802.926547] Btrfs detected SSD devices,