public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: dm-devel@redhat.com, linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.31-rc4 oops in fsnotify extending logical volume
Date: Thu, 30 Jul 2009 12:40:16 +0300	[thread overview]
Message-ID: <4A716A80.5020907@redhat.com> (raw)
In-Reply-To: <200907292313.47762.rjw@sisk.pl>

On 07/30/2009 12:13 AM, Rafael J. Wysocki wrote:
> On Wednesday 29 July 2009, Avi Kivity wrote:
>    
>> # lvextend -L +50G /dev/vg0/images
>>      
>
> I guess this is a regression?
>
>    

It's never happened to me before, and I extend volumes regularly, so I'd 
say it's a regression.  On the other hand after a reboot the command 
worked with the same kernel.

-- 
error compiling committee.c: too many arguments to function


      reply	other threads:[~2009-07-30  9:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-29 15:20 2.6.31-rc4 oops in fsnotify extending logical volume Avi Kivity
2009-07-29 21:13 ` Rafael J. Wysocki
2009-07-30  9:40   ` Avi Kivity [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4A716A80.5020907@redhat.com \
    --to=avi@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@sisk.pl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox