Re: Btrfs fs not mounting or being identified after power loss.
Hello, I've already recreated btrfs on the partition, so there'd be nothing useful to send. Thanks. On Thu, Jan 10, 2013 at 10:13 PM, David Sterba dste...@suse.cz wrote: On Wed, Jan 09, 2013 at 10:43:24PM -0500, Randy Barlow wrote: -BEGIN PGP SIGNED MESSAGE- kernel is at 3.6.11-1-ARCH Sorry I don't know much to help you, but I would suggest perhaps using a newer kernel in the future. It sounds like your FS might be in trouble as is, but I would recommend using the most recent RC kernel (3.8-rc3) and restoring your data to a new btrfs from backups. In general, it's a good idea to stick to pretty recent kernels with btrfs. There are some problems with the 3.8-rc kernels, please do not use them yet, and I don't think that kernel upgrade would help in Jordan's case. david -- To unsubscribe from this list: send the line unsubscribe linux-btrfs in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line unsubscribe linux-btrfs in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Btrfs fs not mounting or being identified after power loss.
Hello, btrfs-progs is at 91d9eec1ff044394f2b98ee7fcb76713dd33b994 kernel is at 3.6.11-1-ARCH Thanks. On Wed, Jan 9, 2013 at 10:01 AM, Randy Barlow ra...@electronsweatshop.com wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/08/2013 12:40 AM, Jordan Windsor wrote: If you need anymore information please ask. Kernel and btrfs-tools versions? - -- R -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlDsrFwACgkQw3vjPfF7QfWLUgCdFiJE4zTHeG3rxqlojSZ+Qid3 +CEAoInZeeawLa9Blh7/bYhXx0LK++sa =oJtF -END PGP SIGNATURE- -- To unsubscribe from this list: send the line unsubscribe linux-btrfs in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line unsubscribe linux-btrfs in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Btrfs fs not mounting or being identified after power loss.
Hello, The power to my computer was suddenly cut, one of my btrfs fs (not the root) has somewhat disappeared, I can't mount it or use any of the available btrfs tools on it. Here's some command output: [root@archpc ~]# fdisk -l /dev/sdb Disk /dev/sdb: 808.9 GB, 80614912 bytes, 1579860576 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x000db8c9 Device Boot Start End Blocks Id System /dev/sdb1 63 1567571967 783785952+ 83 Linux /dev/sdb4 1567571968 1579859967 6144000 82 Linux swap / Solaris /dev/sdb1 is the lost btrfs fs. [root@archpc ~]# btrfs-find-root -v /dev/sdb1 No valid Btrfs found on /dev/sdb1 [root@archpc ~]# btrfsck /dev/sdb1 No valid Btrfs found on /dev/sdb1 [root@archpc ~]# mount /dev/sdb1 /mnt/restore/ mount: wrong fs type, bad option, bad superblock on /dev/sdb1, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so [ 1767.655429] JBD2: no valid journal superblock found [ 1767.655432] EXT4-fs (sdb1): error loading journal If you need anymore information please ask. Thanks. -- To unsubscribe from this list: send the line unsubscribe linux-btrfs in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: parent transid verify failed on -- After moving btrfs closer to the beginning of drive with dd
Also here's the output of btrfs-find-root: ./btrfs-find-root /dev/sdb1 Super think's the tree root is at 1229060866048, chunk root 1259695439872 Went past the fs size, exiting Not sure where to go from here. On Sat, Dec 29, 2012 at 6:04 AM, Jordan Windsor jorda...@gmail.com wrote: Hello, thanks for the response! Here's the output of -o recovery [ 5473.725751] device label Storage devid 1 transid 116023 /dev/sdb1 [ 5473.726612] btrfs: enabling auto recovery [ 5473.726615] btrfs: disk space caching is enabled [ 5473.734581] parent transid verify failed on 1229060423680 wanted 116023 found 116027 [ 5473.734797] parent transid verify failed on 1229060423680 wanted 116023 found 116027 [ 5473.734801] btrfs: failed to read tree root on sdb1 [ 5473.735010] parent transid verify failed on 1229060423680 wanted 116023 found 116027 [ 5473.735259] parent transid verify failed on 1229060423680 wanted 116023 found 116027 [ 5473.735262] btrfs: failed to read tree root on sdb1 [ 5473.756367] parent transid verify failed on 1229060243456 wanted 116022 found 116028 [ 5473.761968] parent transid verify failed on 1229060243456 wanted 116022 found 116028 [ 5473.761975] btrfs: failed to read tree root on sdb1 [ 5475.561208] btrfs bad tree block start 7479324919942847850 1241518882816 [ 5475.567008] btrfs bad tree block start 13410158725948676859 1241518882816 [ 5475.567056] Failed to read block groups: -5 [ 5475.570200] btrfs: open_ctree failed I'm on kernel 3.6.10 and have been before this problem. Thanks. On Sat, Dec 29, 2012 at 5:29 AM, cwillu cwi...@cwillu.com wrote: On Fri, Dec 28, 2012 at 12:09 PM, Jordan Windsor jorda...@gmail.com wrote: Hello, I moved my btrfs to the beginning of my drive updated the partition table also restarted, I'm currently unable to mount it, here's the output in dmesg. [ 481.513432] device label Storage devid 1 transid 116023 /dev/sdb1 [ 481.514277] btrfs: disk space caching is enabled [ 481.522611] parent transid verify failed on 1229060423680 wanted 116023 found 116027 [ 481.522789] parent transid verify failed on 1229060423680 wanted 116023 found 116027 [ 481.522790] btrfs: failed to read tree root on sdb1 [ 481.523656] btrfs: open_ctree failed What command should I run from here? The filesystem wasn't uncleanly unmounted, likely on an older kernel. Try mounting with -o recovery -- To unsubscribe from this list: send the line unsubscribe linux-btrfs in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: parent transid verify failed on -- After moving btrfs closer to the beginning of drive with dd
Hello, thanks for the response! Here's the output of -o recovery [ 5473.725751] device label Storage devid 1 transid 116023 /dev/sdb1 [ 5473.726612] btrfs: enabling auto recovery [ 5473.726615] btrfs: disk space caching is enabled [ 5473.734581] parent transid verify failed on 1229060423680 wanted 116023 found 116027 [ 5473.734797] parent transid verify failed on 1229060423680 wanted 116023 found 116027 [ 5473.734801] btrfs: failed to read tree root on sdb1 [ 5473.735010] parent transid verify failed on 1229060423680 wanted 116023 found 116027 [ 5473.735259] parent transid verify failed on 1229060423680 wanted 116023 found 116027 [ 5473.735262] btrfs: failed to read tree root on sdb1 [ 5473.756367] parent transid verify failed on 1229060243456 wanted 116022 found 116028 [ 5473.761968] parent transid verify failed on 1229060243456 wanted 116022 found 116028 [ 5473.761975] btrfs: failed to read tree root on sdb1 [ 5475.561208] btrfs bad tree block start 7479324919942847850 1241518882816 [ 5475.567008] btrfs bad tree block start 13410158725948676859 1241518882816 [ 5475.567056] Failed to read block groups: -5 [ 5475.570200] btrfs: open_ctree failed I'm on kernel 3.6.10 and have been before this problem. Thanks. On Sat, Dec 29, 2012 at 5:29 AM, cwillu cwi...@cwillu.com wrote: On Fri, Dec 28, 2012 at 12:09 PM, Jordan Windsor jorda...@gmail.com wrote: Hello, I moved my btrfs to the beginning of my drive updated the partition table also restarted, I'm currently unable to mount it, here's the output in dmesg. [ 481.513432] device label Storage devid 1 transid 116023 /dev/sdb1 [ 481.514277] btrfs: disk space caching is enabled [ 481.522611] parent transid verify failed on 1229060423680 wanted 116023 found 116027 [ 481.522789] parent transid verify failed on 1229060423680 wanted 116023 found 116027 [ 481.522790] btrfs: failed to read tree root on sdb1 [ 481.523656] btrfs: open_ctree failed What command should I run from here? The filesystem wasn't uncleanly unmounted, likely on an older kernel. Try mounting with -o recovery -- To unsubscribe from this list: send the line unsubscribe linux-btrfs in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: What's the minimum size I can shrink my FS to?
On Tue, Nov 6, 2012 at 9:45 AM, David Sterba d...@jikos.cz wrote: On Sat, Nov 03, 2012 at 03:10:52PM +1030, Jordan Windsor wrote: [root@archpc ~]# btrfs fi df /home/jordan/Storage/ Data: total=580.88GB, used=490.88GB This is getting full, 84%, there is not much chance of getting rid of substantially many 1G-chunks through the 'usage=1' balance filter. Some of the space between 490G and 580G will be spent on slack space and fragmentation, the rest may be packed together by a higher usage= value (but will be slower due to relocating more data). System, DUP: total=32.00MB, used=76.00KB System: total=4.00MB, used=0.00 Metadata, DUP: total=13.01GB, used=1001.83MB If you intend to shrink a filesystem, all space group types must be taken into account, so here you have at least 580G + 2x32M + 4M + 2x13G = ~607G [root@archpc ~]# btrfs fi sh failed to read /dev/sr0 Label: 'Storage' uuid: 717d4a43-38b3-495f-841b-d223068584de Total devices 1 FS bytes used 491.86GB devid1 size 612.04GB used 606.96GB path /dev/sda6 ^^ confirmed :) So basically you cannot go under this number when shrinking. I think you can squeeze the metadata space down to 2G (or maybe to 1G, it's getting very close to 1G so hard to guess) by the -musage= filter AND using at least 3.7 kernel (or 3.6+ chris' for-linus branch) with the fixed over-allocation bug (otherwise the size will stay pinned at 2% of the filesystem size). david Thanks for the info! Shame I can't save space though. Thanks anyway. -- To unsubscribe from this list: send the line unsubscribe linux-btrfs in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
What's the minimum size I can shrink my FS to?
Hello, I'm trying to shrink my Btrfs filesystem to the smallest size it can go, here's the information: failed to read /dev/sr0 Label: 'Storage' uuid: 717d4a43-38b3-495f-841b-d223068584de Total devices 1 FS bytes used 491.86GB devid1 size 612.04GB used 605.98GB path /dev/sda6 Btrfs Btrfs v0.19 Data: total=580.90GB, used=490.88GB System, DUP: total=32.00MB, used=76.00KB System: total=4.00MB, used=0.00 Metadata, DUP: total=12.51GB, used=1001.61MB Here's the command I use to resize: [root@archpc ~]# btrfs file res 500g /home/jordan/Storage/ Resize '/home/jordan/Storage/' of '500g' ERROR: unable to resize '/home/jordan/Storage/' - No space left on device I was wondering if that size doesn't work then what's the minimum I can shrink to? Thanks. -- To unsubscribe from this list: send the line unsubscribe linux-btrfs in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: What's the minimum size I can shrink my FS to?
Hello, here's the new output: [root@archpc ~]# btrfs bal start -musage=1 -dusage=1 /home/jordan/Storage/ Done, had to relocate 3 out of 609 chunks [root@archpc ~]# btrfs fi df /home/jordan/Storage/ Data: total=580.88GB, used=490.88GB System, DUP: total=32.00MB, used=76.00KB System: total=4.00MB, used=0.00 Metadata, DUP: total=13.01GB, used=1001.83MB [root@archpc ~]# btrfs fi sh failed to read /dev/sr0 Label: 'Storage' uuid: 717d4a43-38b3-495f-841b-d223068584de Total devices 1 FS bytes used 491.86GB devid1 size 612.04GB used 606.96GB path /dev/sda6 Btrfs Btrfs v0.19 [root@archpc ~]# btrfs file res 500g /home/jordan/Storage/ Resize '/home/jordan/Storage/' of '500g' ERROR: unable to resize '/home/jordan/Storage/' - No space left on device Thanks. (Had to resend forgot to CC the mailing list, sorry) On Sat, Nov 3, 2012 at 3:09 PM, Jordan Windsor jorda...@gmail.com wrote: Hello, here's the new output: [root@archpc ~]# btrfs bal start -musage=1 -dusage=1 /home/jordan/Storage/ Done, had to relocate 3 out of 609 chunks [root@archpc ~]# btrfs fi df /home/jordan/Storage/ Data: total=580.88GB, used=490.88GB System, DUP: total=32.00MB, used=76.00KB System: total=4.00MB, used=0.00 Metadata, DUP: total=13.01GB, used=1001.83MB [root@archpc ~]# btrfs fi sh failed to read /dev/sr0 Label: 'Storage' uuid: 717d4a43-38b3-495f-841b-d223068584de Total devices 1 FS bytes used 491.86GB devid1 size 612.04GB used 606.96GB path /dev/sda6 Btrfs Btrfs v0.19 [root@archpc ~]# btrfs file res 500g /home/jordan/Storage/ Resize '/home/jordan/Storage/' of '500g' ERROR: unable to resize '/home/jordan/Storage/' - No space left on device Thanks. On Sat, Nov 3, 2012 at 2:43 PM, cwillu cwi...@cwillu.com wrote: Run btrfs balance start -musage=1 -dusage=1, and then try it again. This may require update btrfs tools however. On Fri, Nov 2, 2012 at 10:09 PM, Jordan Windsor jorda...@gmail.com wrote: Hello, I'm trying to shrink my Btrfs filesystem to the smallest size it can go, here's the information: failed to read /dev/sr0 Label: 'Storage' uuid: 717d4a43-38b3-495f-841b-d223068584de Total devices 1 FS bytes used 491.86GB devid1 size 612.04GB used 605.98GB path /dev/sda6 Btrfs Btrfs v0.19 Data: total=580.90GB, used=490.88GB System, DUP: total=32.00MB, used=76.00KB System: total=4.00MB, used=0.00 Metadata, DUP: total=12.51GB, used=1001.61MB Here's the command I use to resize: [root@archpc ~]# btrfs file res 500g /home/jordan/Storage/ Resize '/home/jordan/Storage/' of '500g' ERROR: unable to resize '/home/jordan/Storage/' - No space left on device I was wondering if that size doesn't work then what's the minimum I can shrink to? Thanks. -- To unsubscribe from this list: send the line unsubscribe linux-btrfs in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line unsubscribe linux-btrfs in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: WARNING: at fs/btrfs/free-space-cache.c:1887 after hard shutdown.
On Wed, Jun 27, 2012 at 11:18 PM, Josef Bacik jba...@fusionio.com wrote: On Tue, Jun 26, 2012 at 09:46:44PM -0600, Jordan Windsor wrote: Hello, My computer locked up and I had to press the reset button. Ever since then I can't mount the btrfs filesystem, here's the output: Already fixed, go to the newest kernel you can get ahold of, 3.5-rc4 is the newest I think? Thanks, Josef Hello, I get the same problem with linux-mainline from AUR (latest), When I try mounting with -o clear_cache the process hangs and I can't c-Z or c-C it also I can't kill it in another terminal either. Thanks. -- To unsubscribe from this list: send the line unsubscribe linux-btrfs in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: at fs/btrfs/free-space-cache.c:1887 after hard shutdown.
Hello, My computer locked up and I had to press the reset button. Ever since then I can't mount the btrfs filesystem, here's the output: [ 37.645583] [ cut here ] [ 37.645598] WARNING: at fs/btrfs/free-space-cache.c:1887 btrfs_remove_free_space+0x329/0x350 [btrfs]() [ 37.645600] Modules linked in: btrfs zlib_deflate libcrc32c ext4 jbd2 mbcache crc16 snd_hda_codec_realtek rc_dib0700_rc5 mt2266 dvb_usb_dib0700 dib3000mc dib8000 dib0070 dib7000m dib7000p dibx000_common dib0090 dvb_usb dvb_core rc_core microcode joydev usb_storage uas coretemp acpi_cpufreq mperf ppdev nvidia(PO) 8139too 8139cp mii iTCO_wdt i2c_i801 i2c_core iTCO_vendor_support serio_raw i7core_edac edac_core evdev pcspkr processor parport_pc parport snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_page_alloc snd_timer snd soundcore button reiserfs aes_x86_64 cryptd aes_generic xts gf128mul dm_crypt dm_mod usbhid hid sr_mod sd_mod cdrom pata_jmicron pata_acpi uhci_hcd ata_piix ata_generic ahci libahci libata ehci_hcd crc32c_intel usbcore scsi_mod usb_common floppy [ 37.645651] Pid: 304, comm: mount Tainted: P O 3.4.4-2-ck #1 [ 37.645653] Call Trace: [ 37.645659] [810515cf] warn_slowpath_common+0x7f/0xc0 [ 37.645662] [8105162a] warn_slowpath_null+0x1a/0x20 [ 37.645670] [a0f4a159] btrfs_remove_free_space+0x329/0x350 [btrfs] [ 37.645674] [81073bb0] ? abort_exclusive_wait+0xb0/0xb0 [ 37.645682] [a0efaa6f] btrfs_alloc_logged_file_extent+0x1bf/0x1e0 [btrfs] [ 37.645688] [a0ee7bfa] ? btrfs_free_path+0x2a/0x40 [btrfs] [ 37.645697] [a0f44c5e] replay_one_extent+0x5be/0x620 [btrfs] [ 37.645701] [81179f55] ? iput+0x105/0x210 [ 37.645710] [a0f4549b] replay_one_buffer+0x27b/0x350 [btrfs] [ 37.645719] [a0f302bd] ? alloc_extent_buffer+0x9d/0x5c0 [btrfs] [ 37.645728] [a0f42d92] walk_down_log_tree+0x202/0x3c0 [btrfs] [ 37.645736] [a0f42fed] walk_log_tree+0x9d/0x1f0 [btrfs] [ 37.645745] [a0f46f4b] btrfs_recover_log_trees+0x21b/0x3a0 [btrfs] [ 37.645754] [a0f45220] ? replay_one_dir_item+0xe0/0xe0 [btrfs] [ 37.645763] [a0f0883d] open_ctree+0x14ed/0x1ac0 [btrfs] [ 37.645767] [8121e101] ? disk_name+0x61/0xc0 [ 37.645773] [a0ee5836] btrfs_mount+0x5b6/0x6a0 [btrfs] [ 37.645776] [8113f400] ? alloc_pages_current+0xb0/0x120 [ 37.645780] [81163533] mount_fs+0x43/0x1b0 [ 37.645783] [8117d740] vfs_kern_mount+0x70/0x100 [ 37.645786] [8117dc64] do_kern_mount+0x54/0x110 [ 37.645788] [8117f55a] do_mount+0x26a/0x850 [ 37.645791] [81101e1e] ? __get_free_pages+0xe/0x50 [ 37.645794] [8117f15a] ? copy_mount_options+0x3a/0x180 [ 37.645797] [8117fc7d] sys_mount+0x8d/0xe0 [ 37.645801] [814626e9] system_call_fastpath+0x16/0x1b [ 37.645802] ---[ end trace 98bf42a1cdef3f88 ]--- [ 37.645812] [ cut here ] [ 37.646716] kernel BUG at fs/btrfs/extent-tree.c:6107! [ 37.647722] invalid opcode: [#1] PREEMPT SMP [ 37.648763] CPU 1 [ 37.649156] Modules linked in: btrfs zlib_deflate libcrc32c ext4 jbd2 mbcache crc16 snd_hda_codec_realtek rc_dib0700_rc5 mt2266 dvb_usb_dib0700 dib3000mc dib8000 dib0070 dib7000m dib7000p dibx000_common dib0090 dvb_usb dvb_core rc_core microcode joydev usb_storage uas coretemp acpi_cpufreq mperf ppdev nvidia(PO) 8139too 8139cp mii iTCO_wdt i2c_i801 i2c_core iTCO_vendor_support serio_raw i7core_edac edac_core evdev pcspkr processor parport_pc parport snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_page_alloc snd_timer snd soundcore button reiserfs aes_x86_64 cryptd aes_generic xts gf128mul dm_crypt dm_mod usbhid hid sr_mod sd_mod cdrom pata_jmicron pata_acpi uhci_hcd ata_piix ata_generic ahci libahci libata ehci_hcd crc32c_intel usbcore scsi_mod usb_common floppy [ 37.665300] [ 37.665591] Pid: 304, comm: mount Tainted: PW O 3.4.4-2-ck #1 [ 37.666973] RIP: 0010:[a0efaa77] [a0efaa77] btrfs_alloc_logged_file_extent+0x1c7/0x1e0 [btrfs] [ 37.669058] RSP: 0018:880118649748 EFLAGS: 00010282 [ 37.670098] RAX: ffea RBX: 88010ff1a000 RCX: 000e [ 37.671495] RDX: RSI: 0046 RDI: 88010fef6840 [ 37.672892] RBP: 8801186497c8 R08: R09: [ 37.674289] R10: R11: R12: 880118649883 [ 37.675687] R13: R14: 0019cf4be000 R15: 88010fc95800 [ 37.731396] FS: 7fb10edfb740() GS:88011fc4() knlGS: [ 37.788242] CS: 0010 DS: ES: CR0: 8005003b [ 37.788243] CR2: 7f5b18c9c15c CR3: 000110a7d000 CR4: 07e0 [ 37.788245] DR0: DR1: DR2: [ 37.788247] DR3: DR6: 0ff0 DR7:
Errors in dmesg, no crashes though.
Hello, I'm running Ubuntu under KVM, with btrfs on the host where the Qemu/KVM image is stored, the VM was also running at the time. I was going to check something unrelated in the dmesg output, as I did that I noticed some errors in it about btrfs here they are: [ 4294.431807] btrfs: block rsv returned -28 [ 4294.431811] [ cut here ] [ 4294.431831] WARNING: at fs/btrfs/extent-tree.c:5985 btrfs_alloc_free_block+0x344/0x350 [btrfs]() [ 4294.431835] Modules linked in: xfs exportfs jfs kvm_intel kvm fuse btrfs zlib_deflate crc32c libcrc32c ext4 jbd2 mbcache crc16 snd_hda_codec_realtek rc_dib0700_rc5 mt2266 ir_lirc_codec lirc_dev ir_mce_kbd_decoder ir_sony_decoder ir_jvc_decoder dvb_usb_dib0700 ir_rc6_decoder dib3000mc dib8000 dib0070 dib7000m dib0090 dib7000p dibx000_common ir_rc5_decoder ir_nec_decoder usb_storage uas dvb_usb dvb_core rc_core joydev snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_page_alloc snd_timer ppdev parport_pc nvidia(P) snd soundcore i2c_i801 serio_raw evdev parport floppy 8139too 8139cp iTCO_wdt i7core_edac edac_core pcspkr button processor i2c_core iTCO_vendor_support mii reiserfs aes_x86_64 cryptd aes_generic xts gf128mul dm_crypt dm_mod usbhid hid sd_mod sr_mod pata_jmicron cdrom ahci libahci ata_piix uhci_hcd pata_acpi libata scsi_mod ehci_hcd usbcore usb_common [ 4294.431967] Pid: 10505, comm: btrfs-endio-wri Tainted: P O 3.2.7-1-ARCH #1 [ 4294.431969] Call Trace: [ 4294.431974] [8106609f] warn_slowpath_common+0x7f/0xc0 [ 4294.431976] [810660fa] warn_slowpath_null+0x1a/0x20 [ 4294.431982] [a0f95fd4] btrfs_alloc_free_block+0x344/0x350 [btrfs] [ 4294.431986] [a0f84e62] __btrfs_cow_block+0x122/0x430 [btrfs] [ 4294.431991] [a0f85266] btrfs_cow_block+0xf6/0x250 [btrfs] [ 4294.431997] [a0fd42e0] ? btrfs_set_lock_blocking_rw+0x50/0xb0 [btrfs] [ 4294.432002] [a0f88dde] btrfs_search_slot+0x18e/0x8a0 [btrfs] [ 4294.432007] [a0fe0614] ? tree_insert+0x84/0x1e0 [btrfs] [ 4294.432013] [a0f9a374] btrfs_lookup_csum+0x74/0x170 [btrfs] [ 4294.432016] [81152183] ? kmem_cache_alloc+0x133/0x160 [ 4294.432022] [a0f9b3c4] btrfs_csum_file_blocks+0xb4/0x680 [btrfs] [ 4294.432029] [a0faaa99] ? insert_reserved_file_extent.constprop.52+0x219/0x270 [btrfs] [ 4294.432035] [a0fa8f35] add_pending_csums.isra.38+0x45/0x60 [btrfs] [ 4294.432042] [a0fabdff] btrfs_endio_direct_write+0x1ff/0x300 [btrfs] [ 4294.432045] [8119bc4d] bio_endio+0x1d/0x40 [ 4294.432050] [a0f9e736] end_workqueue_fn+0x56/0x140 [btrfs] [ 4294.432056] [a0fce920] worker_loop+0x150/0x520 [btrfs] [ 4294.432059] [8104d788] ? __wake_up_common+0x58/0x90 [ 4294.432065] [a0fce7d0] ? btrfs_queue_worker+0x300/0x300 [btrfs] [ 4294.432127] [8108842c] kthread+0x8c/0xa0 [ 4294.432131] [8145f5f4] kernel_thread_helper+0x4/0x10 [ 4294.432133] [810883a0] ? kthread_worker_fn+0x190/0x190 [ 4294.432135] [8145f5f0] ? gs_change+0x13/0x13 [ 4294.432136] ---[ end trace 4afe986ec803a741 ]--- [ 4294.432146] btrfs: block rsv returned -28 [ 4294.432147] [ cut here ] [ 4294.432152] WARNING: at fs/btrfs/extent-tree.c:5985 btrfs_alloc_free_block+0x344/0x350 [btrfs]() [ 4294.432153] Modules linked in: xfs exportfs jfs kvm_intel kvm fuse btrfs zlib_deflate crc32c libcrc32c ext4 jbd2 mbcache crc16 snd_hda_codec_realtek rc_dib0700_rc5 mt2266 ir_lirc_codec lirc_dev ir_mce_kbd_decoder ir_sony_decoder ir_jvc_decoder dvb_usb_dib0700 ir_rc6_decoder dib3000mc dib8000 dib0070 dib7000m dib0090 dib7000p dibx000_common ir_rc5_decoder ir_nec_decoder usb_storage uas dvb_usb dvb_core rc_core joydev snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_page_alloc snd_timer ppdev parport_pc nvidia(P) snd soundcore i2c_i801 serio_raw evdev parport floppy 8139too 8139cp iTCO_wdt i7core_edac edac_core pcspkr button processor i2c_core iTCO_vendor_support mii reiserfs aes_x86_64 cryptd aes_generic xts gf128mul dm_crypt dm_mod usbhid hid sd_mod sr_mod pata_jmicron cdrom ahci libahci ata_piix uhci_hcd pata_acpi libata scsi_mod ehci_hcd usbcore usb_common [ 4294.432186] Pid: 10505, comm: btrfs-endio-wri Tainted: PW O 3.2.7-1-ARCH #1 [ 4294.432187] Call Trace: [ 4294.432189] [8106609f] warn_slowpath_common+0x7f/0xc0 [ 4294.432191] [810660fa] warn_slowpath_null+0x1a/0x20 [ 4294.432196] [a0f95fd4] btrfs_alloc_free_block+0x344/0x350 [btrfs] [ 4294.432203] [a0fc5fb0] ? read_extent_buffer+0xb0/0x190 [btrfs] [ 4294.432207] [a0f84e62] __btrfs_cow_block+0x122/0x430 [btrfs] [ 4294.432212] [a0f85266] btrfs_cow_block+0xf6/0x250 [btrfs] [ 4294.432217] [a0fd42e0] ? btrfs_set_lock_blocking_rw+0x50/0xb0 [btrfs] [ 4294.43] [a0f88dde] btrfs_search_slot+0x18e/0x8a0 [btrfs] [ 4294.432227] [a0fe0614] ? tree_insert+0x84/0x1e0 [btrfs] [ 4294.432293] [a0f9a374]
Grow btrfs partition filesystem backwards
Hello, I was wondering how I would go about growing a btrfs filesystem backwards, I don't have any space to store the files temporally, I'd need to do it in place. Thanks. -- To unsubscribe from this list: send the line unsubscribe linux-btrfs in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Unable to resize btrfs filesystem
Hello, I'm currently running Linux 3.0.7 (release -1 under Arch 64bit) and btrfs-progs-unstable 0.19.20101006-1, I'm trying to resize my btrfs filesystem on /dev/sdb6, the partition has the room to allow expansion here's the output of btrfs fi sh: failed to read /dev/sr0 Label: none uuid: db1a36b3-5047-4c14-8f67-262c2d63fcb8 Total devices 1 FS bytes used 388.51GB devid1 size 477.29GB used 416.29GB path /dev/sda6 Label: none uuid: d8685e5e-c9ba-4ba5-a147-0c2caf8f4b2d Total devices 1 FS bytes used 101.81GB devid1 size 552.08GB used 109.54GB path /dev/md127 Label: 'Storage2' uuid: 34115fbe-e9e3-4691-a3c6-715f5d30b4e5 Total devices 1 FS bytes used 196.73GB devid1 size 336.00GB used 336.00GB path /dev/sdb6 The command I'm running to resize the filesystem is su -c btrfs fi re 1:max /home/jordan/Storage/Storage2/ and here's the output: Resize '/home/jordan/Storage/Storage2/' of '1:max' ERROR: unable to resize '/home/jordan/Storage/Storage2/ Thanks. -- To unsubscribe from this list: send the line unsubscribe linux-btrfs in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Find RAID level, Change RAID level.
On Sun, Oct 30, 2011 at 6:40 AM, Helmut Hullen hul...@t-online.de wrote: Hallo, Jordan, Du meintest am 30.10.11: I was wondering is it possible to find the RAID level currently in use by a btrfs volume, also can I change the data metadata (or either) RAID levels after creation. To see the RAID levels, use btrfs fi df /path/to/filesystem I've just run that command on my system: Data, RAID0: total=3.81TB, used=3.71TB System, RAID1: total=16.00MB, used=244.00KB System: total=4.00MB, used=0.00 Metadata, RAID1: total=16.25GB, used=4.78GB And that shows what I have defined via mkfs.btrfs: ... --data raid0 --metadata raid1 What tells your system? What do you want to be installed? Viele Gruesse! Helmut -- To unsubscribe from this list: send the line unsubscribe linux-btrfs in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Thanks, It currently shows this: Data: total=195.01GB, used=193.93GB System, DUP: total=8.00MB, used=28.00KB System: total=4.00MB, used=0.00 Metadata, DUP: total=1.75GB, used=385.41MB Metadata: total=8.00MB, used=0.00 I didn't specify any RAID levels during creation. I'd like to have a RAID0 installation across two hard drives. -- To unsubscribe from this list: send the line unsubscribe linux-btrfs in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Find RAID level, Change RAID level.
On Mon, Oct 31, 2011 at 12:36 AM, Ilya Dryomov idryo...@gmail.com wrote: On Mon, Oct 31, 2011 at 12:10:34AM +1030, Jordan Windsor wrote: Thanks, It currently shows this: Data: total=195.01GB, used=193.93GB System, DUP: total=8.00MB, used=28.00KB System: total=4.00MB, used=0.00 Metadata, DUP: total=1.75GB, used=385.41MB Metadata: total=8.00MB, used=0.00 I didn't specify any RAID levels during creation. I'd like to have a RAID0 installation across two hard drives. How many devices do you have in your FS right now ? If it's only 1 then add another one (btrfs device add dev path to FS) and run balance (btrfs fi balance path to FS). That should give you raid0 for data across two drives w/o applying any patches. Thanks, Ilya -- To unsubscribe from this list: send the line unsubscribe linux-btrfs in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Thanks, I was wondering if I added a device that was already part of another btrfs volume, then would I have the files merged as one volume or overwritten in the newly added one? -- To unsubscribe from this list: send the line unsubscribe linux-btrfs in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Find RAID level, Change RAID level.
Hello, I was wondering is it possible to find the RAID level currently in use by a btrfs volume, also can I change the data metadata (or either) RAID levels after creation. Thanks. -- To unsubscribe from this list: send the line unsubscribe linux-btrfs in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Find RAID level, Change RAID level.
On Sun, Oct 30, 2011 at 1:14 AM, Hugo Mills h...@carfax.org.uk wrote: On Sun, Oct 30, 2011 at 01:06:49AM +1030, Jordan Windsor wrote: On Sun, Oct 30, 2011 at 1:04 AM, Hugo Mills h...@carfax.org.uk wrote: On Sun, Oct 30, 2011 at 12:55:33AM +1030, Jordan Windsor wrote: On Sun, Oct 30, 2011 at 12:43 AM, Hugo Mills h...@carfax.org.uk wrote: On Sun, Oct 30, 2011 at 12:28:39AM +1030, Jordan Windsor wrote: Hello, I was wondering is it possible to find the RAID level currently in use by a btrfs volume, also can I change the data metadata (or either) RAID levels after creation. To see the RAID levels, use btrfs fi df /path/to/filesystem To change RAID levels, you will need Ilya Dryomov's restriper patches, which were posted to this list back in August. Thanks, so If it mentions DUP on the metadata system line I'm using RAID1? No, DUP is two copies of the data (or metadata), but kept on the same block device. If the word RAID isn't mentioned, I'm in single mode for both metadata data? If there's nothing at all, then it's single. If it says DUP, then you have two redundant copies, but they could both be on the same block device, so it'll protect you from a bad block or out-of-band data corruption, but not from the loss of the whole disk. Hugo. -- === Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk === PGP key: 515C238D from wwwkeys.eu.pgp.net or http://www.carfax.org.uk --- Ceci est un travail pour l'Australien. --- Just curious, If I go with RAID1 will I still get the speed boost that comes along with RAID0? (Read from both drives) Thanks. -- To unsubscribe from this list: send the line unsubscribe linux-btrfs in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
