linux-kernel - Re: btrfs io errors on 3.4rc1

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 2 Apr 2012 17:26:08 -0400
From:	Chris Mason <chris.mason@...cle.com>
To:	Dave Jones <davej@...hat.com>,
	Linux Kernel <linux-kernel@...r.kernel.org>,
	linux-btrfs@...r.kernel.org
Subject: Re: btrfs io errors on 3.4rc1

On Mon, Apr 02, 2012 at 05:16:22PM -0400, Dave Jones wrote:
> On Mon, Apr 02, 2012 at 03:48:14PM -0400, Chris Mason wrote:
>  > On Mon, Apr 02, 2012 at 02:02:14PM -0400, Dave Jones wrote:
>  > > Updated to rc1 this morning, and my machines with btrfs are all freaking out..
>  > > 
>  > > I got this from my cron email ..
>  > > 
>  > > /etc/cron.daily/prelink: line 41: /var/lib/prelink/full: Input/output error
>  > > cp: cannot create regular file `/var/lib/prelink/quick': Input/output error
>  > > /etc/cron.daily/prelink: line 45: /var/log/prelink/prelink.log: Input/output error
>  > 
>  > That's not good.  Can you please try my for-linus branch against 3.3?
>  > That will rules out all the shiny new btrfs code.
>  > 
>  > git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git for-linus
>  > 
>  > -chris
> 
> Broken.
> 
> (17:14:52:davej@...p-189-232:~)$ fsx foo
> truncating to largest ever: 0x13e76
> truncating to largest ever: 0x2e52c
> ftruncate1: 2e52c
> dotruncate: ftruncate: Input/output error
> Segmentation fault (core dumped)

Huh.  x86-32 or x86-64?  I know you said there were no interesting
messages, but could you please send the messages you did get?

-chris

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/