public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
* xfs_repair fatal error -- name create failed in lost+found, filesystem may be out of space
@ 2013-10-17  3:57 Viet Nguyen
  2013-10-17  4:06 ` Dave Chinner
  0 siblings, 1 reply; 4+ messages in thread
From: Viet Nguyen @ 2013-10-17  3:57 UTC (permalink / raw)
  To: xfs


[-- Attachment #1.1: Type: text/plain, Size: 261 bytes --]

Hi,
Me again. I've got get another corrupted drive and I'm getting a different
error for xfs_repair:

fatal error -- name create failed in lost+found (117), filesystem may be
out of space

When mounted the filesystem is only 53% used.

Any ideas?

Thanks,
Viet

[-- Attachment #1.2: Type: text/html, Size: 418 bytes --]

[-- Attachment #2: Type: text/plain, Size: 121 bytes --]

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: xfs_repair fatal error -- name create failed in lost+found, filesystem may be out of space
  2013-10-17  3:57 xfs_repair fatal error -- name create failed in lost+found, filesystem may be out of space Viet Nguyen
@ 2013-10-17  4:06 ` Dave Chinner
  2013-10-17 17:01   ` Viet Nguyen
  0 siblings, 1 reply; 4+ messages in thread
From: Dave Chinner @ 2013-10-17  4:06 UTC (permalink / raw)
  To: Viet Nguyen; +Cc: xfs

On Wed, Oct 16, 2013 at 08:57:20PM -0700, Viet Nguyen wrote:
> Hi,
> Me again. I've got get another corrupted drive and I'm getting a different
> error for xfs_repair:
> 
> fatal error -- name create failed in lost+found (117), filesystem may be
> out of space

Error 117 is telling you that the filesystem is corrupted. i.e.
attempting to make a new name for a lost inode has resulted in
detection of a new corruption or previously undetected or
uncorrected corruption in the filesystem.

Given the amount of damage your filesystem sustained, that's not
totally unexpected, especially if you are running 3.2.0-alpha.
Can you provide more details about the failure?

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: xfs_repair fatal error -- name create failed in lost+found, filesystem may be out of space
  2013-10-17  4:06 ` Dave Chinner
@ 2013-10-17 17:01   ` Viet Nguyen
  2013-10-29 20:52     ` Viet Nguyen
  0 siblings, 1 reply; 4+ messages in thread
From: Viet Nguyen @ 2013-10-17 17:01 UTC (permalink / raw)
  To: Dave Chinner; +Cc: xfs


[-- Attachment #1.1: Type: text/plain, Size: 1386 bytes --]

The corruption was detected after a power outage. The underlying system is
an LSI RAID 6, according to the controller, the RAID integrity checks out,
though I don't know if I could trust that. This is the second time this
server has suffered xfs corruption after a power outage. The strange thing
is that there hasn't been any writes made to the filesystem for weeks. The
server passed a memtest, and xfs_repair fails consistently at the same
point. So I'm not sure what's going on there.

Is there any other particular details I could provide?


On Wed, Oct 16, 2013 at 9:06 PM, Dave Chinner <david@fromorbit.com> wrote:

> On Wed, Oct 16, 2013 at 08:57:20PM -0700, Viet Nguyen wrote:
> > Hi,
> > Me again. I've got get another corrupted drive and I'm getting a
> different
> > error for xfs_repair:
> >
> > fatal error -- name create failed in lost+found (117), filesystem may be
> > out of space
>
> Error 117 is telling you that the filesystem is corrupted. i.e.
> attempting to make a new name for a lost inode has resulted in
> detection of a new corruption or previously undetected or
> uncorrected corruption in the filesystem.
>
> Given the amount of damage your filesystem sustained, that's not
> totally unexpected, especially if you are running 3.2.0-alpha.
> Can you provide more details about the failure?
>
> Cheers,
>
> Dave.
> --
> Dave Chinner
> david@fromorbit.com
>

[-- Attachment #1.2: Type: text/html, Size: 1946 bytes --]

[-- Attachment #2: Type: text/plain, Size: 121 bytes --]

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: xfs_repair fatal error -- name create failed in lost+found, filesystem may be out of space
  2013-10-17 17:01   ` Viet Nguyen
@ 2013-10-29 20:52     ` Viet Nguyen
  0 siblings, 0 replies; 4+ messages in thread
From: Viet Nguyen @ 2013-10-29 20:52 UTC (permalink / raw)
  To: Dave Chinner; +Cc: xfs


[-- Attachment #1.1: Type: text/plain, Size: 1568 bytes --]

Sorry to be a pain, but is there anything I can do?


On Thu, Oct 17, 2013 at 10:01 AM, Viet Nguyen <vietnguyen@gmail.com> wrote:

> The corruption was detected after a power outage. The underlying system is
> an LSI RAID 6, according to the controller, the RAID integrity checks out,
> though I don't know if I could trust that. This is the second time this
> server has suffered xfs corruption after a power outage. The strange thing
> is that there hasn't been any writes made to the filesystem for weeks. The
> server passed a memtest, and xfs_repair fails consistently at the same
> point. So I'm not sure what's going on there.
>
> Is there any other particular details I could provide?
>
>
> On Wed, Oct 16, 2013 at 9:06 PM, Dave Chinner <david@fromorbit.com> wrote:
>
>> On Wed, Oct 16, 2013 at 08:57:20PM -0700, Viet Nguyen wrote:
>> > Hi,
>> > Me again. I've got get another corrupted drive and I'm getting a
>> different
>> > error for xfs_repair:
>> >
>> > fatal error -- name create failed in lost+found (117), filesystem may be
>> > out of space
>>
>> Error 117 is telling you that the filesystem is corrupted. i.e.
>> attempting to make a new name for a lost inode has resulted in
>> detection of a new corruption or previously undetected or
>> uncorrected corruption in the filesystem.
>>
>> Given the amount of damage your filesystem sustained, that's not
>> totally unexpected, especially if you are running 3.2.0-alpha.
>> Can you provide more details about the failure?
>>
>> Cheers,
>>
>> Dave.
>> --
>> Dave Chinner
>> david@fromorbit.com
>>
>
>

[-- Attachment #1.2: Type: text/html, Size: 2419 bytes --]

[-- Attachment #2: Type: text/plain, Size: 121 bytes --]

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2013-10-29 20:52 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-10-17  3:57 xfs_repair fatal error -- name create failed in lost+found, filesystem may be out of space Viet Nguyen
2013-10-17  4:06 ` Dave Chinner
2013-10-17 17:01   ` Viet Nguyen
2013-10-29 20:52     ` Viet Nguyen

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox