From: Iustin Pop <iusty@k1024.org>
To: Wengang Wang <wen.gang.wang@oracle.com>
Cc: greg.marsden@oracle.com, joe.jin@oracle.com, xfs@oss.sgi.com
Subject: Re: do we support using a file as logdev?
Date: Tue, 20 Apr 2010 17:27:06 +0200 [thread overview]
Message-ID: <20100420152706.GA4548@teal.hq.k1024.org> (raw)
In-Reply-To: <20100420143656.GA3634@laptop.oracle.com>
On Tue, Apr 20, 2010 at 10:36:56PM +0800, Wengang Wang wrote:
> Hi experts,
>
> Do we support using a file as log device?
> If no, it's strange that we support running xfs on a file but don't support log
> file.
Have you tried using losetup and passing the loop device instead?
regards,
iustin
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-04-20 15:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-20 14:36 do we support using a file as logdev? Wengang Wang
2010-04-20 15:27 ` Iustin Pop [this message]
2010-04-20 16:09 ` Wengang Wang
2010-04-20 17:01 ` Eric Sandeen
2010-04-21 3:03 ` 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=20100420152706.GA4548@teal.hq.k1024.org \
--to=iusty@k1024.org \
--cc=greg.marsden@oracle.com \
--cc=joe.jin@oracle.com \
--cc=wen.gang.wang@oracle.com \
--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