| To: | "Barry Naujok" <bnaujok@xxxxxxx> |
|---|---|
| Subject: | Re: xfs_repair phase6 repeatedly dies : name create failed in lost+found (117), filesystem may be out of space |
| From: | "Peter Gervai" <grinapo@xxxxxxxxx> |
| Date: | Fri, 5 Oct 2007 08:44:45 +0200 |
| Cc: | "xfs@xxxxxxxxxxx" <xfs@xxxxxxxxxxx> |
| Dkim-signature: | v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=Q6MKj2aBGEMuSFMrZqG1Uo4fTeNHBs6CZzqfA/WavOQ=; b=YhA6ORB9BJG67F1OaQZ8XzX38KE0j8KQtEOvl0klgARVuEEASjfTwkhnziV62cKcq3+E2cpKfVv7RHiHzgX1iV/hBKxLgxZdNUfMYxZeHmHLNFG0GBt909dluYJid92BQenNWiDmF6CuhNVHUwEXe3KCVMKcCDp/FXkxlCk2q2k= |
| Domainkey-signature: | a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Kp+cosJvUHE0Tvnun6RPeVI9tpEFtZMSl3xEzF5aYTS16AvfQRZRIsZEFCeM6JZ2wNCnTM2srvInZS3dSYJHfQYVHlY0OofrjOxwFTeTsIv3Lut5q1CMXt73+3mrN9ROBMzmsof8WcVlqLIsmQsBJTs3/MVgNZiZk2ZWzDKbBn4= |
| In-reply-to: | <op.tzo76uks3jf8g2@pc-bnaujok.melbourne.sgi.com> |
| References: | <d55656c10710041510y79cac2abv1c4d30d3afe1949f@mail.gmail.com> <op.tzo76uks3jf8g2@pc-bnaujok.melbourne.sgi.com> |
| Sender: | xfs-bounce@xxxxxxxxxxx |
On 10/5/07, Barry Naujok <bnaujok@xxxxxxx> wrote:
> On Fri, 05 Oct 2007 08:10:49 +1000, Peter Gervai <grinapo@xxxxxxxxx> wrote:
>
> > Hello,
> >
> > xfs_repair in Debian sid (v2.9.0) repeatedly dies on a poor filesystem
> > with that message:
> >
> > fatal error -- name create failed in lost+found (117), filesystem may
> > be out of space
> >
> > The filesystem is not out of space:
> >
> > Filesystem 1K-blocks Used Available
> > Use% Mounted on
> > /dev/mapper/vg0-backup 419379200 144029144 275350056 35%
> > /var/lib/backuppc
> >
> > I tried to find error 117 but it seems to be well hidden. :-) I try
> > newer xfs_repair but I doubt it'll help. Any idea?
>
> Can you do a "df -i" as well?
Yes:
Filesystem Inodes IUsed IFree IUse% Mounted on
/dev/mapper/vg0-backup
419430400 3475741 415954659 1% /var/lib/backuppc
> The other option is to run xfs_metadump from xfsprogs 2.9.4 so I can
> perform some analysis as to why it's failing.
Errrmm...
# xfs_metadump -wg /dev/vg0/backup vg0.backup.metadump
Copied 158208 of 3719360 inodes (0 of 1 AGs)
/usr/sbin/xfs_metadump: line 31: 1778 Segmentation fault (core
dumped) xfs_db$DBOPTS -i -p xfs_metadump -c "metadump$OPTS $2" $1
Do you want the partial dump, or should I try something tricky?
--
byte-byte,
grin
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Reading directory entries from BMAP, cyjoyp |
|---|---|
| Next by Date: | Re: RFC: Case-insensitive support for XFS, Christoph Hellwig |
| Previous by Thread: | Re: xfs_repair phase6 repeatedly dies : name create failed in lost+found (117), filesystem may be out of space, Barry Naujok |
| Next by Thread: | Huge return on FRLE today, patrickfrederick |
| Indexes: | [Date] [Thread] [Top] [All Lists] |