All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wengang Wang <wen.gang.wang@oracle.com>
To: xfs@oss.sgi.com
Cc: greg.marsden@oracle.com, joe.jin@oracle.com, wen.gang.wang@oracle.com
Subject: do we support using a file as logdev?
Date: Tue, 20 Apr 2010 22:36:56 +0800	[thread overview]
Message-ID: <20100420143656.GA3634@laptop.oracle.com> (raw)

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.
If yes, it fails at mount.

[root@desk test-xfsprogs]# mkfs.xfs
-llogdev=/root/test-xfsprogs/test-xfsprogs-tmp/imagefile,size=32768b
/dev/sda10 -f
meta-data=/dev/sda10             isize=256    agcount=4, agsize=1250558
blks
         =                       sectsz=512   attr=2
data     =                       bsize=4096   blocks=5002231, imaxpct=25
         =                       sunit=0      swidth=0 blks
naming   =version 2              bsize=4096   ascii-ci=0
log      =/root/test-xfsprogs/test-xfsprogs-tmp/imagefile bsize=4096
blocks=32768, version=2
         =                       sectsz=512   sunit=0 blks, lazy-count=0
realtime =none                   extsz=4096   blocks=0, rtextents=0
[root@desk test-xfsprogs]# mount
-ologdev=/root/test-xfsprogs/test-xfsprogs-tmp/imagefile /dev/sda10 /xfs
mount: the kernel does not recognize /dev/sda10 as a block device
       (maybe `insmod driver'?)

regards,
wengang.

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

             reply	other threads:[~2010-04-20 14:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-20 14:36 Wengang Wang [this message]
2010-04-20 15:27 ` do we support using a file as logdev? Iustin Pop
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=20100420143656.GA3634@laptop.oracle.com \
    --to=wen.gang.wang@oracle.com \
    --cc=greg.marsden@oracle.com \
    --cc=joe.jin@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 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.