On Apr 18, 2010, at 11:46 AM, Bernd Schubert wrote:
You don't need to take the filesystem offline for lfsck.
You sure about that? Looking at
http://wiki.lustre.org/manual/LustreManual18_HTML/LustreRecovery.html#50598012_37365
step 1 says Stop the Lustre File System.
Also, I have
On Apr 18, 2010, at 1:14 PM, Andreas Dilger wrote:
On 2010-04-18, at 07:16, Charles Taylor wrote:
On Apr 18, 2010, at 9:35 AM, Miguel Afonso Oliveira wrote:
You are going to have to use unlink with something like this:
for file in lost_files
unlink $file
Nope. That's really no
...@lists.lustre.org] On Behalf Of Andreas Dilger
Sent: Sunday, April 18, 2010 11:14 AM
To: Charles Taylor
Cc: Lustre User Discussion Mailing List
Subject: Re: [Lustre-discuss] Lost Files - How to remove from MDT
On 2010-04-18, at 07:16, Charles Taylor wrote:
On Apr 18, 2010, at 9:35 AM, Miguel Afonso
We lost an OST several months ago and could not recover it.We decided to
deactivate until we bring some new storage online and can just rebuild the
entire file system.However, now, the MDT still knows about all the files
that were on the lost OST and this results in things like invalid
Hi,
You are going to have to use unlink with something like this:
for file in lost_files
unlink $file
Cheers,
Miguel Afonso Oliveira
P.S.: To build a list of all your lost files you can do a rsync with the
dry-run flag.
On Apr 18, 2010, at 2:30 PM, Charles Taylor wrote:
We lost an
On Sun, 2010-04-18 at 09:30 -0400, Charles Taylor wrote:
Is there some way to remove these files from the MDT - as though they never
existed - without reformatting the entire file system?
lfsck is the documented, supported method.
b.
signature.asc
Description: This is a digitally signed
On Apr 18, 2010, at 9:38 AM, Brian J. Murrell wrote:
On Sun, 2010-04-18 at 09:30 -0400, Charles Taylor wrote:
Is there some way to remove these files from the MDT - as though they never
existed - without reformatting the entire file system?
lfsck is the documented, supported method.
On Apr 18, 2010, at 9:35 AM, Miguel Afonso Oliveira wrote:
Hi,
You are going to have to use unlink with something like this:
for file in lost_files
unlink $file
Nope. That's really no different than rm and produces the same result...
unlink
On Apr 18, 2010, at 10:47 AM, Miguel Afonso Oliveira wrote:
Hi again,
Sorry I forgot to mention this only works if the offending OST still
exists. If at this time you can no longer re-include the OST where these
files existed then you can still
create a new one with the same index and
On Sunday 18 April 2010, Charles Taylor wrote:
On Apr 18, 2010, at 9:38 AM, Brian J. Murrell wrote:
On Sun, 2010-04-18 at 09:30 -0400, Charles Taylor wrote:
Is there some way to remove these files from the MDT - as though they
never existed - without reformatting the entire file system?
On 2010-04-18, at 07:16, Charles Taylor wrote:
On Apr 18, 2010, at 9:35 AM, Miguel Afonso Oliveira wrote:
You are going to have to use unlink with something like this:
for file in lost_files
unlink $file
Nope. That's really no different than rm and produces the same
result...
Hi all,
I had a similar problem with one of my filesystems and from my experience until
the actual OST, or another one with the same original index, is present, unlink
will not work.
It will give the error message an it will keep on showing the reference to the
file.
At the time it somehow
While I'm thinking about it, that brings up an interesting question. All the
OSTs for this file system were originally formatted under 1.6.3. We have
since upgraded to 1.8.x. If we reformat the missing OST with the same index
under 1.8.2 and add it back into the file system (sans its
13 matches
Mail list logo
