All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Marcin Zajączkowski" <mszpak@wp.pl>
To: chatz@melbourne.sgi.com
Cc: linux-xfs@oss.sgi.com
Subject: Re: Errors on XFS partition - ask for diagnose
Date: Tue, 28 Nov 2006 19:00:07 +0100	[thread overview]
Message-ID: <456C7927.6070501@wp.pl> (raw)
In-Reply-To: <456AA1D4.6020303@melbourne.sgi.com>

On 2006-11-27 9:29:08 +0100, David Chatterton wrote:
> See:
> http://oss.sgi.com/projects/xfs/faq.html#dir2

Thanks, I had 2.6.17 kernel those days.
I'll try to get xfs_repair >= 2.8.10 for SystemRescueCD which I use and 
try repair file system.


Regards
Marcin


> Marcin Zajączkowski wrote:
>> Hi,
>>
>>
>> Recently some of my executable files (on XFS partition) have become
>> "invisible" for whereis, locate, find, bash, mc, nautilus and others.
>> They are not reported by autofill in bash, but I can run it by typing
>> full file name. "ls" with full name returns info about file, "ls" with
>> regexp no.
>>
>> I run xfs_check and it returned me many errors (see below).
>>
>> Because I don't have experience with errors on XFS partition I would
>> like to ask, do you think that after ran of xfs_repair file system would
>> be still usable (now only those files are invisible, but still accessible)?
>>
>>
>> Btw, I didn't have any power failure, nor problems with hardware (at
>> least on this partition - based on smart report). The trigger for that
>> was to fill in partition in 100%. Could it cause those error on my
>> partition?
(...)

      parent reply	other threads:[~2006-11-28 19:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-26 21:02 Errors on XFS partition - ask for diagnose Marcin Zajączkowski
2006-11-27 13:46 ` Chris Wedgwood
     [not found] ` <456AA1D4.6020303@melbourne.sgi.com>
2006-11-28 18:00   ` Marcin Zajączkowski [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=456C7927.6070501@wp.pl \
    --to=mszpak@wp.pl \
    --cc=chatz@melbourne.sgi.com \
    --cc=linux-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.