WARNING at fs/btrfs/extent_io.c:3618 write_extent_buffer (sparc64)

When mounting a newly created btrfs on sparc64, the following warning is printed (vanilla 2.6.33-rc6, Feb 03): [ 1087.724622] [ cut here ] [ 1087.779337] WARNING: at /data/scm/linux-2.6-git/fs/btrfs/extent_io.c:3618 write_extent_buffer+0x140/0x1a0 [btrfs]() [ 1087.903973]

Re: WARNING at fs/btrfs/extent_io.c:3618 write_extent_buffer (sparc64)

On Fri, Feb 05, 2010 at 02:43:01AM -0800, Christian Kujau wrote: > When mounting a newly created btrfs on sparc64, the following warning is > printed (vanilla 2.6.33-rc6, Feb 03): Ok, I've got a sparc box on the way, and I'll cleanup these errors. -chris -- To unsubscribe from this list: send th

Kernel unaligned access at TPC[10101f18] btrfs_csum_final+0x38/0x60

When writing to a newly created btrfs (vanilla 2.6.33-rc6, sparc64) the following messages are printed: [28617.650231] Kernel unaligned access at TPC[10101f18] btrfs_csum_final+0x38/0x60 [btrfs] [28617.745783] Kernel unaligned access at TPC[10101f18] btrfs_csum_final+0x38/0x60 [btrfs] [28654.5

Re: Kernel unaligned access at TPC[10101f18] btrfs_csum_final+0x38/0x60

From: Christian Kujau Date: Fri, 5 Feb 2010 10:36:52 -0800 (PST) > When writing to a newly created btrfs (vanilla 2.6.33-rc6, sparc64) the > following messages are printed: > > [28617.650231] Kernel unaligned access at TPC[10101f18] > btrfs_csum_final+0x38/0x60 [btrfs] > [28617.745783] Kernel

semantics in btrfs multi-device (RAID) mount-by-disk-label ?

i created a array, mkfs.btrfs -L TEST -m raid10 -d raid10 /dev/sda /dev/sdb /dev/sdc /dev/sdd btrfs-show Label: TEST uuid: 85aa9ac8-0089-4dd3-b8b2-3c0cbb96c924 Total devices 4 FS bytes used 28.00KB devid3 size 931.51GB used 2.01GB path /dev/sdc

Re: when/why to use diffferent raid values for btrfs data & metadata?

anyone on when/why to use different RAID geometries for data & metadata? On Sun, Jan 24, 2010 at 8:38 AM, 0bo0 <0.bugs.onl...@gmail.com> wrote: > hi > > On Sun, Jan 24, 2010 at 3:28 AM, RK wrote: >> try this article "Linux Don't Need No Stinkin' ZFS: BTRFS Intro & >> Benchmarks" >> http://www.lin

does btrfs have RAID I/O throughput (un)limiting sysctls, similar to md?

i've a 4 drive array connected via a PCIe SATA card. per OS (opensuse) default, md RAID I/O performance was being limited by, cat /proc/sys/dev/raid/speed_limit_min 1000 cat /proc/sys/dev/raid/speed_limit_max 20 changing, echo "dev.raid.speed_limit_min=10" >> /etc/sysctl.c

Re: Kernel unaligned access at TPC[10101f18] btrfs_csum_final+0x38/0x60

On Fri, 5 Feb 2010 at 12:01, David Miller wrote: > Can you rerun your test with the following patch applied? > It will obtain more information for the btrfs developers. Thanks, David! Here it is: [ 1861.965178] Kernel unaligned access at TPC[10101f18] btrfs_csum_final+0x38/0x60 [btrfs] [ 1862.06

Re: Kernel unaligned access at TPC[10101f18] btrfs_csum_final+0x38/0x60

From: Christian Kujau Date: Fri, 5 Feb 2010 21:13:00 -0800 (PST) > On Fri, 5 Feb 2010 at 12:01, David Miller wrote: >> Can you rerun your test with the following patch applied? >> It will obtain more information for the btrfs developers. > > Thanks, David! Here it is: > > [ 1861.965178] Kernel

Re: Kernel unaligned access at TPC[10101f18] btrfs_csum_final+0x38/0x60

On Fri, 5 Feb 2010 at 21:32, David Miller wrote: > My debugging patch didn't work correctly. > Can you try using this one instead? Hm, now it looks like this, but I don't know how it'd reveal more information: [ 210.707051] Kernel unaligned access at TPC[10101f18] btrfs_csum_final+0x38/0x60 [b

Re: Kernel unaligned access at TPC[10101f18] btrfs_csum_final+0x38/0x60

From: Christian Kujau Date: Fri, 5 Feb 2010 22:28:47 -0800 (PST) > Hm, now it looks like this, but I don't know how it'd reveal more > information: > > [ 210.707051] Kernel unaligned access at TPC[10101f18] > btrfs_csum_final+0x38/0x60 [btrfs] > [ 210.802236] Caller [10101f1c:btrfs_csum_fina