From: Fabio Massimo Di Nitto <fabbione@ubuntu.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] GFS2 OOPS at mount with 2.6.24-rc1 + nwm
Date: Fri, 26 Oct 2007 10:56:26 +0200 [thread overview]
Message-ID: <4721ABBA.7080904@ubuntu.com> (raw)
Hi Steven,
Extremely simple setup, 3 nodes cluster, no services or anything fancy. One
shared block device (aoe + vblade) on 2.6.24-rc1.
mkfs.gfs2 -j 6 -p lock_dlm -t gutsy:gfs2 /dev/etherd/e0.0
This will destroy any data on /dev/etherd/e0.0.
Are you sure you want to proceed? [y/n] y
Device: /dev/etherd/e0.0
Blocksize: 4096
Device Size 1.00 GB (262144 blocks)
Filesystem Size: 1.00 GB (262142 blocks)
Journals: 6
Resource Groups: 4
Locking Protocol: "lock_dlm"
Lock Table: "gutsy:gfs2"
root at node3:~# mount -t gfs2 /dev/etherd/e0.0 /mnt/gfs2
OOPS is in attachment.
Last commit from linux-2.6.git: ade8c56cbd02020fecbe1684f181250a466685eb
x86 bitops: fix code style issues
Last commit from -nwm: 237b88c5dca962668273fc4f2f3d45c00756a948
[GFS2] Use correct include file in ops_address.c
Cheers
Fabio
--
I'm going to make him an offer he can't refuse.
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: OOPS
URL: <http://listman.redhat.com/archives/cluster-devel/attachments/20071026/013760c2/attachment.ksh>
reply other threads:[~2007-10-26 8:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4721ABBA.7080904@ubuntu.com \
--to=fabbione@ubuntu.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;
as well as URLs for NNTP newsgroup(s).