From: Federico Sevilla III <jijo@free.net.ph>
To: linux-kernel@vger.kernel.org, linux-xfs@oss.sgi.com
Subject: Re: [2.6.12] XFS: Undeletable directory
Date: Tue, 21 Jun 2005 09:15:52 +0800 [thread overview]
Message-ID: <20050621011552.GC4927@free.net.ph> (raw)
In-Reply-To: <200506201225.11129.lkml@kcore.org>
On Mon, Jun 20, 2005 at 12:25:10PM +0200, Jan De Luyck wrote:
> On Monday 20 June 2005 09:04, Nathan Scott wrote:
> > If it comes to it, you can always zero out individual inode fields
> > for that inode in xfs_db (with -x option to enable write mode) and
> > then xfs_repair should be able to get past it.
>
> Any idea how this should be set?
# xfs_db -x -c 'inode XXX' -c 'write core.nextents 0' -c 'write core.size 0' /dev/hdXX
Cheers!
--> Jijo
--
Federico Sevilla III : jijo.free.net.ph : When we speak of free software
GNU/Linux Specialist : GnuPG 0x93B746BE : we refer to freedom, not price.
prev parent reply other threads:[~2005-06-21 1:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-19 17:04 [2.6.12] XFS: Undeletable directory Jan De Luyck
[not found] ` <Pine.LNX.4.63.0506191924430.7686@hobbybop>
2005-06-19 18:34 ` Jan De Luyck
2005-06-19 23:02 ` Valdis.Kletnieks
2005-06-20 10:20 ` Jan De Luyck
2005-06-20 7:04 ` Nathan Scott
2005-06-20 10:25 ` Jan De Luyck
2005-06-21 1:15 ` Federico Sevilla III [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=20050621011552.GC4927@free.net.ph \
--to=jijo@free.net.ph \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox