All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Walker <walker@stsci.edu>
To: Emmanuel Florac <eflorac@intellique.com>
Cc: xfs@oss.sgi.com
Subject: Re: Should xfs_repair take this long?
Date: Thu, 15 Mar 2007 11:27:47 -0400	[thread overview]
Message-ID: <45F965F3.10902@stsci.edu> (raw)
In-Reply-To: <20070315162333.72f34d58@harpe.intellique.com>


    I checked the status of the LVM before starting xfs_repair.  I can't 
promise it's all in order, but at least the various pvdisplay, 
vgdisplay, lvdisplay, etc all came back normal.  So... I'll just wait a 
few days and hope that xfs_repair comes back with something eventually.

    thanks for at least taking an interest, too bad that there's nothing 
we can really do about it.

    Thomas Walker

Emmanuel Florac wrote:

>Le Thu, 15 Mar 2007 11:08:00 -0400
>Thomas Walker <walker@stsci.edu> écrivait:
>
>  
>
>>    So if I see I/O activity and cpu activity, which I do, should I 
>>assume that eventually the repair should return? 
>>    
>>
>
>The repair _MAY_ return, unfortunately...
>
>  
>
>> We are thinking of 
>>interrupting it and trying to add more memory and restarting it.
>>Maybe we should just let it go. 
>>    
>>
>
>Yes, let it go now...
>
>  
>
>>If you think it might finish some
>>time, even if it's going to be another day or two, then I'm willing
>>to be patient. I'm just worried it might be going around in circles.
>>
>>    
>>
>
>It should finish if you're testing the right device, and the LV is
>properly assembled. If it reach the end of the device and find nothing,
>you should restart LVM first to check that your PV/VG/LV are correctly
>set up, and retry.
>If it doesn't work after that, backup will be your last friend.
>
>  
>

  reply	other threads:[~2007-03-15 15:27 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-15 11:27 Should xfs_repair take this long? Thomas Walker
2007-03-15 14:04 ` Emmanuel Florac
2007-03-15 14:06   ` Thomas Walker
     [not found]     ` <20070315160309.652a6e0c@harpe.intellique.com>
     [not found]       ` <45F96150.50001@stsci.edu>
2007-03-15 15:23         ` Emmanuel Florac
2007-03-15 15:27           ` Thomas Walker [this message]
2007-03-15 23:10     ` David Chinner
2007-03-16 15:15       ` Thomas Walker
2007-03-16 19:37         ` David Chinner
  -- strict thread matches above, loose matches on Subject: below --
2007-03-16  0:20 Thomas Walker
2007-03-16  1:32 ` David Chinner
2007-03-16 11:15   ` Thomas Walker
2007-03-16 19:20     ` David Chinner
2007-03-16 19:30       ` Eric Sandeen
2007-03-16 20:09 Thomas Walker
2007-03-16 20:52 ` David Chinner

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=45F965F3.10902@stsci.edu \
    --to=walker@stsci.edu \
    --cc=eflorac@intellique.com \
    --cc=xfs@oss.sgi.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.