From: Christoph Hellwig <hch@lst.de>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Mounting lock_nolock file systems?
Date: Tue, 21 Jun 2022 14:58:57 +0200 [thread overview]
Message-ID: <20220621125857.GA6999@lst.de> (raw)
In-Reply-To: <97a9a768-1915-f532-09a4-99ee78a639ae@redhat.com>
On Tue, Jun 21, 2022 at 12:19:02PM +0100, Andrew Price wrote:
> On 21/06/2022 10:14, Christoph Hellwig wrote:
>> I'm felling a little stupid, but in the past after a
>>
>> mkfs.gfs2 -O -p lock_nolock
>>
>> I could just mount the created file system locally.
>>
>> On current mainline that does not seem to work any more, what am I
>> missing?
>
> I can't reproduce the problem on current mainline. What version of
> gfs2-utils is your mkfs.gfs2 from?
Sorry, actually it was the pagecache for-next branch from willy. Looks
like mainline itself is fine.
I'll try to get the superblock information from the pagecache branch
once I find a little time, chasing a bunch of other bugs in the meantime.
next prev parent reply other threads:[~2022-06-21 12:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-21 9:14 [Cluster-devel] Mounting lock_nolock file systems? Christoph Hellwig
2022-06-21 10:53 ` Andreas Gruenbacher
2022-06-21 11:19 ` Andrew Price
2022-06-21 12:58 ` Christoph Hellwig [this message]
2022-06-22 14:30 ` Christoph Hellwig
2022-06-23 15:44 ` Andreas Gruenbacher
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=20220621125857.GA6999@lst.de \
--to=hch@lst.de \
/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.