From: Wengang Wang <wen.gang.wang@oracle.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: Christoph Hellwig <hch@infradead.org>,
xfs@oss.sgi.com, greg.marsden@oracle.com, joe.jin@oracle.com,
Wengang Wang <wen.gang.wang@oracle.com>
Subject: Re: is realtime device supported?
Date: Fri, 23 Apr 2010 11:00:11 +0800 [thread overview]
Message-ID: <20100423030011.GB2949@laptop.oracle.com> (raw)
In-Reply-To: <4BD07F06.70101@sandeen.net>
On 10-04-22 11:53, Eric Sandeen wrote:
> Christoph Hellwig wrote:
> > On Thu, Apr 22, 2010 at 10:49:39PM +0800, Wengang Wang wrote:
> >> Do we support realtime device?
> >>
> >> I got the following error:
> >
> > It sounds like you do not have CONFIG_XFS_RT enable in your kernel
> > configuration. But to answer your original question the realtime
> > device is not supported in the sense of actively maintained. The
> > code is still there, but more or less for legacy reasons. I would
> > not recommend it for new installations.
Yes, CONFIG_XFS_RT is disabled.
[wwg@desk linux-2.6.18.x86_64]$ grep CONFIG_XFS_RT .config
# CONFIG_XFS_RT is not set
And Ok I see. Also should we add the point to man page of mkfs.xfs?
>
> Agreed.
>
> FWIW, dmesg probably gave you a more helpful error message than
> mount...
>
> cmn_err(CE_WARN, "XFS: RT mount failed");
>
> hm or maybe not ;)
Only "XFS: RT mount failed" :)
Thanks all!
regards,
wengang.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-04-23 2:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-22 14:49 is realtime device supported? Wengang Wang
2010-04-22 16:23 ` Christoph Hellwig
2010-04-22 16:53 ` Eric Sandeen
2010-04-23 3:00 ` Wengang Wang [this message]
2010-04-23 3:19 ` Eric Sandeen
2010-04-25 10:08 ` Wengang Wang
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=20100423030011.GB2949@laptop.oracle.com \
--to=wen.gang.wang@oracle.com \
--cc=greg.marsden@oracle.com \
--cc=hch@infradead.org \
--cc=joe.jin@oracle.com \
--cc=sandeen@sandeen.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox