From: Christoph Hellwig <hch@lst.de>
To: xfs@oss.sgi.com
Subject: rfc: kill ino64 mount option
Date: Fri, 27 Jun 2008 17:39:28 +0200 [thread overview]
Message-ID: <20080627153928.GA31384@lst.de> (raw)
Does anyone have objections to kill the ino64 mount option? It's purely
a debug tool to force inode numbers outside of the range representable
in 32bits and is quite invasive for something that could easily be
debugged by just having a large enough filesystem..
next reply other threads:[~2008-06-27 15:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-27 15:39 Christoph Hellwig [this message]
2008-06-28 0:09 ` rfc: kill ino64 mount option Dave Chinner
2008-06-28 0:46 ` Mark Goodwin
2008-06-28 4:31 ` Eric Sandeen
2008-06-28 15:25 ` Christoph Hellwig
2008-06-28 19:52 ` Eric Sandeen
2008-07-01 8:07 ` Christoph Litauer
2008-07-01 14:12 ` Mark Goodwin
2008-07-01 14:45 ` Christoph Litauer
2008-06-28 15:23 ` Christoph Hellwig
2008-06-29 23:13 ` Nathan Scott
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=20080627153928.GA31384@lst.de \
--to=hch@lst.de \
--cc=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.