From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Date: Tue, 21 Jun 2022 14:58:57 +0200 Subject: [Cluster-devel] Mounting lock_nolock file systems? In-Reply-To: <97a9a768-1915-f532-09a4-99ee78a639ae@redhat.com> References: <20220621091420.GC3256@lst.de> <97a9a768-1915-f532-09a4-99ee78a639ae@redhat.com> Message-ID: <20220621125857.GA6999@lst.de> List-Id: To: cluster-devel.redhat.com MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit 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.