Re: [PATCH] fs: btrfs: fix potential overflow

2014-08-24 Thread Timofey Titovets
2014-08-24 8:41 GMT+03:00 Brian Norris : > It looks like this intended to be 64-bit arithmetic, but it's actually > performed as 32-bit. Fix that. (Note that 'increment' was being > initialized twice, so this patch removes one of those.) > > Caught by Coverity Scan (CID 1201422). > > Signed-off-by:

6+ MiB/s constant usage on a btrfs volume with kernel 3.16

2014-08-24 Thread Oon-Ee Ng
Hi, I'm using 64-bit Arch Linux. Since update to kernel versions 3.16 and 3.16.1 I'm getting a constant 6+ MiB/s write on my root. Root does not seem to fill up though. Has run for 2 hours straight, and obviously slows everything else down to a crawl. Downgrading to 3.15.8 (last working version f

Re: superblock checksum mismatch after crash, cannot mount

2014-08-24 Thread Leen Besselink
On Sun, Aug 24, 2014 at 12:56:47AM +, Duncan wrote: > Zygo Blaxell posted on Sat, 23 Aug 2014 12:38:05 -0400 as excerpted: > > > Consumer SD cards are /terrible/ storage devices. Always back up all > > data written to an SD card as soon as possible after writing it, and > > develop a process

Re: superblock checksum mismatch after crash, cannot mount

2014-08-24 Thread Chris Samuel
On Sun, 24 Aug 2014 01:08:53 PM Leen Besselink wrote: > tip for basically any Linux filesystem, especially on Flash-based storage > and also btrfs: - use noatime (if you aren't doing that already, don't know > if that is the default in btrfs) Since 2.6.30 (5 years old now) the kernel has defaulte

Re: 6+ MiB/s constant usage on a btrfs volume with kernel 3.16

2014-08-24 Thread Duncan
Oon-Ee Ng posted on Sun, 24 Aug 2014 17:55:32 +0800 as excerpted: > I'm using 64-bit Arch Linux. Since update to kernel versions 3.16 and > 3.16.1 I'm getting a constant 6+ MiB/s write on my root. Root does not > seem to fill up though. Has run for 2 hours straight, and obviously > slows everythin

Re: superblock checksum mismatch after crash, cannot mount

2014-08-24 Thread Duncan
Leen Besselink posted on Sun, 24 Aug 2014 13:08:53 +0200 as excerpted: > tip for basically any Linux filesystem, especially on Flash-based > storage and also btrfs: > - use noatime (if you aren't doing that already, don't know if that is > the default in btrfs) It's not the default for btrfs, but

Re: superblock checksum mismatch after crash, cannot mount

2014-08-24 Thread Florian Gamböck
Am 24.08.2014 13:08, schrieb Leen Besselink: tip for basically any Linux filesystem, especially on Flash-based storage and also btrfs: - use noatime (if you aren't doing that already, don't know if that is the default in btrfs) Yeah, I use this option per standard since I don't really need ac

Re: btrfs unmountable, any btrfs tool segfaults

2014-08-24 Thread Nikolay Shtabel
Thanks for the link, I'm glad to see that restore work for you. I've tried this also and everything doesn't work ending up with segfault. Unfortunately in my case I had some important files on btrfs partition, due to performance reasons (it was on SSD). I doesn't find solution in mailing-list arc

Re: 6+ MiB/s constant usage on a btrfs volume with kernel 3.16

2014-08-24 Thread Oon-Ee Ng
On Sun, Aug 24, 2014 at 8:57 PM, Duncan <1i5t5.dun...@cox.net> wrote: > Oon-Ee Ng posted on Sun, 24 Aug 2014 17:55:32 +0800 as excerpted: > >> I'm using 64-bit Arch Linux. Since update to kernel versions 3.16 and >> 3.16.1 I'm getting a constant 6+ MiB/s write on my root. Root does not >> seem to f

REPORT: Still a lot of BTRFS freezes in 3.16.1-1-ARCH

2014-08-24 Thread Swâmi Petaramesh
Hi there, This is to report that I'm still having quite systematic BRTFS freezes on an ArchLinux running latest 3.16.1-1-ARCH kernel. Interestingly enough, I have several latops with the exact same setup : Arch Linux with 3.16.1-1-ARCH kernel, fully running on BTRFS (with LZO compression) over

Re: REPORT: Still a lot of BTRFS freezes in 3.16.1-1-ARCH

2014-08-24 Thread Tomasz Torcz
On Sun, Aug 24, 2014 at 07:25:43PM +0200, Swâmi Petaramesh wrote: > Hi there, > > This is to report that I'm still having quite systematic BRTFS freezes on an > ArchLinux running latest 3.16.1-1-ARCH kernel. > > Interestingly enough, I have several latops with the exact same setup : > > Arch Li

Re: 6+ MiB/s constant usage on a btrfs volume with kernel 3.16

2014-08-24 Thread Holger Hoffstätte
On Sun, 24 Aug 2014 19:46:41 +0200, Flash ROM wrote: >> Happens a 100% of the time here, annoyingly. As mentioned, 3.15 was >> working for me, and still does. Multiple reboots and it happens >> immediately on boot even before gdm comes up. > Would be logical to do block-level I/O tracing to get id

Re: superblock checksum mismatch after crash, cannot mount

2014-08-24 Thread Flash ROM
About SD cards and somesuch... TL;DR: THINK TWICE before formatting SD cards!!! What is SD card? One or several NAND flash ICs + controller doing wear leveling and interface translation. It does wear leveling and handles flash blocks translation to show you what you expect, making it look like

Re: superblock checksum mismatch after crash, cannot mount

2014-08-24 Thread Florian Gamböck
Am 24.08.2014 18:59, schrieb Flash ROM: About SD cards and somesuch... TL;DR: THINK TWICE before formatting SD cards!!! If you intended to make me hate SD cards then you did a really good job. Bottom line: THINK TWICE before formatting SD cards. I didn't even think once, because actually I

Re: 6+ MiB/s constant usage on a btrfs volume with kernel 3.16

2014-08-24 Thread Flash ROM
> Happens a 100% of the time here, annoyingly. As mentioned, 3.15 was > working for me, and still does. Multiple reboots and it happens > immediately on boot even before gdm comes up. Would be logical to do block-level I/O tracing to get idea WHAT is this IO, right? Try something like echo 1 > /

Re: superblock checksum mismatch after crash, cannot mount

2014-08-24 Thread Chris Murphy
On Aug 24, 2014, at 10:59 AM, Flash ROM wrote: > > 1) Formatting and repartitioning SD card? Generally WORST IDEA EVER. All cameras have a format function, and this function both partitions and formats (creates a filesystem/volume format). If they can get away with it, so can anyone else.

Re: superblock checksum mismatch after crash, cannot mount

2014-08-24 Thread Chris Murphy
On Aug 23, 2014, at 8:14 AM, Florian Gamböck wrote: > > I haven't run any tests on that, so to be safe, I use a MBR table. And yes, > the table was still in order, all three partitions were there, but none of > the filesystems were recognized. Sorry if I confused you. But still I think > it'

Re: 6+ MiB/s constant usage on a btrfs volume with kernel 3.16

2014-08-24 Thread Oon-Ee Ng
On Mon, Aug 25, 2014 at 2:08 AM, Holger Hoffstätte wrote: > On Sun, 24 Aug 2014 19:46:41 +0200, Flash ROM wrote: > >>> Happens a 100% of the time here, annoyingly. As mentioned, 3.15 was >>> working for me, and still does. Multiple reboots and it happens >>> immediately on boot even before gdm com

Re: Distro vs latest kernel for BTRFS?

2014-08-24 Thread Qu Wenruo
Personally, if doing development, compiling from latest stable or integration kernel is my choice. But if not developing the codes, I prefer Arch's core repo, which is about 1~2 weeks late than the stable release. Although somewhat late, but still much newer than most distros' stable repo. (I

Re: 6+ MiB/s constant usage on a btrfs volume with kernel 3.16

2014-08-24 Thread Oon-Ee Ng
On Mon, Aug 25, 2014 at 8:05 AM, Oon-Ee Ng wrote: > On Mon, Aug 25, 2014 at 2:08 AM, Holger Hoffstätte > wrote: >> >> iosnoop: >> http://www.brendangregg.com/blog/2014-07-16/iosnoop-for-linux.html >> >> Probably either a continuing balance or autodefrag vs. systemd's logging. > > Thank you, I'll

Re: backtrace for segfault in btrfs-convert

2014-08-24 Thread Liu Bo
On Sat, Aug 23, 2014 at 01:37:33PM -0400, Zygo Blaxell wrote: > This came from trying to convert a ~1.8T ext4 filesystem with btrfs-progs > master (24cf4d8c3ee924b474f68514e0167cc2e602a48d) on Debian. e2fsck -f > reports no errors on the source filesystem. > > I've done several ext4 conversions b

Re: REPORT: Still a lot of BTRFS freezes in 3.16.1-1-ARCH

2014-08-24 Thread Liu Bo
On Sun, Aug 24, 2014 at 07:32:56PM +0200, Tomasz Torcz wrote: > On Sun, Aug 24, 2014 at 07:25:43PM +0200, Swâmi Petaramesh wrote: > > Hi there, > > > > This is to report that I'm still having quite systematic BRTFS freezes on > > an > > ArchLinux running latest 3.16.1-1-ARCH kernel. > > > > Int

Re: REPORT: Still a lot of BTRFS freezes in 3.16.1-1-ARCH

2014-08-24 Thread Liu Bo
(Cc Swâmi Petaramesh ) On Mon, Aug 25, 2014 at 12:03:21PM +0800, Liu Bo wrote: > On Sun, Aug 24, 2014 at 07:32:56PM +0200, Tomasz Torcz wrote: > > On Sun, Aug 24, 2014 at 07:25:43PM +0200, Swâmi Petaramesh wrote: > > > Hi there, > > > > > > This is to report that I'm still having quite systematic

Re: fuzz testing a 32 bit x86 user mode linux guest brought a BUG in

2014-08-24 Thread Liu Bo
On Thu, Aug 14, 2014 at 11:56:37PM +0200, Toralf Förster wrote: > > Hello, > > a recent kernel brought up this while using trinity inside a x86 UML (stable > Gentoo Linux): Could you please elaborate what options of trinity you're using? thanks, -liubo > > > Aug 14 22:07:06 trinity kernel:

fs corruption report

2014-08-24 Thread Zooko Wilcox-OHearn
Dear people of linux-btrfs: Thank you for btrfs! It is a beautiful thing. I say that in spite of the fact that it seems to have failed and eaten some of my data. I'm writing with two purposes: to get help and advice in recovering my data, to help debug the software. I was running linux 3.12.26 a

Re: [PATCH] btrfs-progs: Do not free dirty extent buffer

2014-08-24 Thread Naohiro Aota
Hi, Filipe David Manana writes: > On Thu, Aug 21, 2014 at 1:07 PM, Naohiro Aota wrote: >> free_some_buffer() should not free dirty extent buffers. They should be >> left for later commit. >> >> Signed-off-by: Naohiro Aota >> --- >> extent_io.c | 2 +- >> 1 file changed, 1 insertion(+), 1 dele

btrfs-progs: initial reference count of extent buffer is correct?

2014-08-24 Thread Naohiro Aota
Hi, list I'm having trouble with my btrfs FS recently and running btrfs check to try to fix the FS. Unfortunately, it aborted with: btrfsck: root-tree.c:81: btrfs_update_root: Assertion `!(ret != 0)' failed. It means that "extent tree root" is not found in "tree root tree"! Then I added btrfs_pr

Re: btrfs-progs: initial reference count of extent buffer is correct?

2014-08-24 Thread Liu Bo
On Mon, Aug 25, 2014 at 02:26:49PM +0900, Naohiro Aota wrote: > Hi, list > > I'm having trouble with my btrfs FS recently and running btrfs check to > try to fix the FS. Unfortunately, it aborted with: > > btrfsck: root-tree.c:81: btrfs_update_root: Assertion `!(ret != 0)' failed. > > It means t