public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Nathan Scott <nscott@aconex.com>
To: Martin Steigerwald <Martin@lichtvoll.de>
Cc: linux-xfs@oss.sgi.com
Subject: Re: [REVIEW 0/2] Case insensitive support for XFS
Date: Mon, 21 Jan 2008 09:30:14 +1100	[thread overview]
Message-ID: <1200868214.9463.274.camel@edge.scott.net.au> (raw)
In-Reply-To: <200801181905.05263.Martin@lichtvoll.de>

On Fri, 2008-01-18 at 19:05 +0100, Martin Steigerwald wrote:
> Hi Barry!
> 
> Am Freitag 18 Januar 2008 schrieb Barry Naujok:
> 
> > There are two mount options for enabling case-insensitivity
> > on a Unicode XFS filesystem:
> >    - "ci" - enables case-insensitivity for file names
> >    - "ciattr" - enables case-insensitivity for extended
> >                 attributes.
> 
> How do I know that I am on an Unicode XFS filesystem. Could I see this 
> with xfs_db -r -c 'sb 0' -c p <device>? Hmm, nothing unicode related in 
> there as far as I can see. The fs was created with 2.6.23, mkfs.xfs 2.9.4 
> and the mkfs options that David suggested.

You'd have created it with the magic (new) mkfs option, and the
xfs_db "version" command would tell you it was enabled.

> Do I need to backup / mkfs / restore to switch to one? I understand that I 

Yes.

> can switch between enable / disable case-insensitivity via a mount 
> option.

No.

>  Would I be able to enable unicode via xfs_db version command or 
> something like it?

Not as far as I know.  It would be more likely implemented as an
extension to xfs_repair I think, if it were ever done (the xfs_db
version command definately wont have the right kind of logic to
enable/disable this).

cheers.

-- 
Nathan

  reply	other threads:[~2008-01-20 22:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-18  4:43 [REVIEW 0/2] Case insensitive support for XFS Barry Naujok
2008-01-18 18:05 ` Martin Steigerwald
2008-01-20 22:30   ` Nathan Scott [this message]
2008-01-21  1:05     ` Barry Naujok
2008-01-21  1:12       ` Nathan Scott
2008-01-21  1:23         ` Barry Naujok
2008-01-21  0:52   ` Barry Naujok
2008-01-19  5:48 ` Eric Sandeen

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=1200868214.9463.274.camel@edge.scott.net.au \
    --to=nscott@aconex.com \
    --cc=Martin@lichtvoll.de \
    --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