Re: btrfs panic - BUG: soft lockup - CPU#0 stuck for 61s! [fs_mark:4573]

2008-06-09 Thread Chris Mason
On Mon, 2008-06-09 at 17:10 -0700, Mingming Cao wrote: > On Sun, 2008-06-08 at 22:37 -0400, Chris Mason wrote: > > On Thu, 05 Jun 2008 13:43:48 -0400 > > Ric Wheeler <[EMAIL PROTECTED]> wrote: > > > > > Chris Mason wrote: > > > > On Mon, Jun 02, 2008 at 01:52:47PM -0400, Ric Wheeler wrote: > > > >

Re: btrfs panic - BUG: soft lockup - CPU#0 stuck for 61s! [fs_mark:4573]

2008-06-09 Thread Mingming Cao
On Sun, 2008-06-08 at 22:37 -0400, Chris Mason wrote: > On Thu, 05 Jun 2008 13:43:48 -0400 > Ric Wheeler <[EMAIL PROTECTED]> wrote: > > > Chris Mason wrote: > > > On Mon, Jun 02, 2008 at 01:52:47PM -0400, Ric Wheeler wrote: > > > > > >> I can reliably get btrfs to panic by running my fs_mark co

Re: btrfs device management

2008-06-09 Thread Christian Hesse
On Monday 09 June 2008, Miguel Sousa Filipe wrote: > On Mon, Jun 9, 2008 at 2:52 PM, Chris Mason <[EMAIL PROTECTED]> wrote: > > mkfs.btrfs already has a way to set the label of the filesystem. > > mkfs.btrfs -L label /dev/ > > > > btrfs-show will show you the labels of any existing filesystems.

Re: btrfs device management

2008-06-09 Thread Chris Mason
On Mon, 2008-06-09 at 18:19 +0200, Christian Hesse wrote: > On Monday 09 June 2008, Miguel Sousa Filipe wrote: > > On Mon, Jun 9, 2008 at 2:52 PM, Chris Mason <[EMAIL PROTECTED]> wrote: > > > mkfs.btrfs already has a way to set the label of the filesystem. > > > mkfs.btrfs -L label /dev/ > > >

Re: btrfs device management

2008-06-09 Thread Miguel Sousa Filipe
On Mon, Jun 9, 2008 at 2:52 PM, Chris Mason <[EMAIL PROTECTED]> wrote: > On Mon, 2008-06-09 at 14:45 +0100, Miguel Sousa Filipe wrote: >> Hi all, >> >> On Mon, Jun 9, 2008 at 11:06 AM, Chris Mason <[EMAIL PROTECTED]> wrote: >> > On Mon, 9 Jun 2008 02:43:58 -0400 >> > Christoph Hellwig <[EMAIL PROTE

Re: btrfs device management

2008-06-09 Thread Chris Mason
On Mon, 2008-06-09 at 14:45 +0100, Miguel Sousa Filipe wrote: > Hi all, > > On Mon, Jun 9, 2008 at 11:06 AM, Chris Mason <[EMAIL PROTECTED]> wrote: > > On Mon, 9 Jun 2008 02:43:58 -0400 > > Christoph Hellwig <[EMAIL PROTECTED]> wrote: > > > >> On Sat, Jun 07, 2008 at 05:53:37PM -0600, > > > >> Yes

Re: btrfs panic - BUG: soft lockup - CPU#0 stuck for 61s! [fs_mark:4573]

2008-06-09 Thread Ric Wheeler
Chris Mason wrote: On Thu, 05 Jun 2008 13:43:48 -0400 Ric Wheeler <[EMAIL PROTECTED]> wrote: Chris Mason wrote: On Mon, Jun 02, 2008 at 01:52:47PM -0400, Ric Wheeler wrote: I can reliably get btrfs to panic by running my fs_mark code on a newly created file system with lots

Re: btrfs device management

2008-06-09 Thread Miguel Sousa Filipe
Hi all, On Mon, Jun 9, 2008 at 11:06 AM, Chris Mason <[EMAIL PROTECTED]> wrote: > On Mon, 9 Jun 2008 02:43:58 -0400 > Christoph Hellwig <[EMAIL PROTECTED]> wrote: > >> On Sat, Jun 07, 2008 at 05:53:37PM -0600, > >> Yes, I plan to work on adding properly designed multiple device >> support for btrf

Re: Bug report, OOPs on weird conditions.. device under mdadm raid1 failed...

2008-06-09 Thread Chris Mason
On Wed, 2008-06-04 at 01:01 +0100, Miguel Sousa Filipe wrote: > Hello, > > I have a Kernel Bug report. > I must warn that this happened on bad hardware.. one disc of a md > raid1 started to fault.. > my dmesg if full of these: > Something rather strange is happening here, but once Btrfs oopses i

Re: Bug Report - crash copying in large file

2008-06-09 Thread Chris Mason
On Fri, 6 Jun 2008 21:22:51 +1000 Bron Gondwana <[EMAIL PROTECTED]> wrote: > > Yes, this was definitely an ENOSPC oops. Sorry, I do plan on > > starting on enospc, it will come right after the tree concurrency. > > Hey, I really don't care that much - I have a duplicate sitting on > reiserfs on

Re: btrfs device management

2008-06-09 Thread Chris Mason
On Mon, 9 Jun 2008 02:43:58 -0400 Christoph Hellwig <[EMAIL PROTECTED]> wrote: > On Sat, Jun 07, 2008 at 05:53:37PM -0600, > Yes, I plan to work on adding properly designed multiple device > support for btrfs and my upcoming similar xfs work. I'll live in > good old mount and libvolume_id. >