public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Fabio Massimo Di Nitto <fabbione@fabbione.net>
To: Riley Williams <rhw@InfraDead.Org>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.19pre10 DevFS + LVM OOPS
Date: Mon, 08 Jul 2002 18:14:37 +0200	[thread overview]
Message-ID: <3D29BA6D.80105@fabbione.net> (raw)
In-Reply-To: Pine.LNX.4.21.0207072338030.9595-100000@Consulate.UFP.CX

Hi Riley,
                here are the results:


trider-g7:/tmp# mkdir X
trider-g7:/tmp# cd X
trider-g7:/tmp/X# mv ../X ../Y
trider-g7:/tmp/X# cd `pwd`
bash: cd: /tmp/X: No such file or directory
trider-g7:/tmp/X# lvcreate -L10M -ntest system
lvcreate -- rounding size up to physical extent boundary
lvcreate -- doing automatic backup of "system"
lvcreate -- logical volume "/dev/system/test" successfully created

trider-g7:/tmp/X#

as you can see there was no problem at all "unfortunatly".

Regards
Fabio

Riley Williams wrote:

>Hi Fabio.
>
>  
>
>>this happend creating a new a lv with the command lvcreate -L512M
>>-ntest system It did 3 times in a row then it worked again. What was
>>strange is that I was in one dir and unfortunalty I don't remember
>>which and it was crashing. I changed dir and then it was working. In
>>the first instance I didn't thought about taking notes but atleast I
>>have a full trace (the machine didn't hang or reboot... it is still
>>alive 100%).
>>    
>>
>
>This may be completely off-track but I've seen it cause wierd problems
>in the past, so worth checking - was the directory you were in when the
>machine crashed one that still existed as far as the file system was
>concerned?
>
>  
>




      parent reply	other threads:[~2002-07-08 16:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-07 18:08 2.4.19pre10 DevFS + LVM OOPS Fabio Massimo Di Nitto
2002-07-07 22:43 ` Riley Williams
2002-07-08  5:34   ` Fabio Massimo Di Nitto
2002-07-08 16:14   ` Fabio Massimo Di Nitto [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=3D29BA6D.80105@fabbione.net \
    --to=fabbione@fabbione.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rhw@InfraDead.Org \
    /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