NetBSD Problem Report #48378

From reinoud@diablo.13thmonkey.org  Wed Nov 13 15:52:01 2013
Return-Path: <reinoud@diablo.13thmonkey.org>
Received: from mail.netbsd.org (mail.netbsd.org [149.20.53.66])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(Client CN "mail.NetBSD.org", Issuer "Postmaster NetBSD.org" (verified OK))
	by mollari.NetBSD.org (Postfix) with ESMTPS id D58E6A619E
	for <gnats-bugs@gnats.NetBSD.org>; Wed, 13 Nov 2013 15:52:00 +0000 (UTC)
Message-Id: <20131113155158.2FFC1C13333@diablo.13thmonkey.org>
Date: Wed, 13 Nov 2013 16:51:58 +0100 (CET)
From: reinoud@NetBSD.org
Reply-To: reinoud@diablo.13thmonkey.org
To: gnats-bugs@NetBSD.org
Subject: LFS can't mount FS newfs_lfs created
X-Send-Pr-Version: 3.95

>Number:         48378
>Category:       kern
>Synopsis:       LFS can't mount FS newfs_lfs created
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    kern-bug-people
>State:          closed
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Nov 13 15:55:00 +0000 2013
>Closed-Date:    Mon May 30 00:07:28 +0000 2016
>Last-Modified:  Mon May 30 00:07:28 +0000 2016
>Originator:     Reinoud Zandijk
>Release:        NetBSD 6.99.23
>Organization:
NetBSD

>Environment:


System: NetBSD diablo.13thmonkey.org 6.99.23 NetBSD 6.99.23 (GENERIC) #6: Sun Jul 7 19:00:12 CEST 2013 root@diablo.13thmonkey.org:/usr/sources/cvs.netbsd.org/src-nilfs/sys/arch/amd64/compile/GENERIC amd64
Architecture: x86_64
Machine: amd64
>Description:
When experimenting with LFS, i tried to create an oddball LFS system to test
for the speed impact of various choices. It newfs'd fine but the kernel
wouldn't mount.

>How-To-Repeat:

diablo# newfs_lfs -b 512k -B 64M /dev/rvnd0a
Creating a version 2 LFS with roll-forward ident 0x5c642b6a
9984.0MB in 156 segments of size 67108864
super-block backups (for fsck -b #) at:
16, 1966080, 3932160, 5898240, 7864320, 9830400, 11796480, 13762560, 15728640,
17694720.

diablo# mount -t lfs /dev/vnd0a /mnt
mount_lfs: /dev/vnd0a on /mnt: incorrect super block
diablo#

>Fix:
Unknown


>Release-Note:

>Audit-Trail:
From: David Holland <dholland-bugs@netbsd.org>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: kern/48378: LFS can't mount FS newfs_lfs created
Date: Wed, 13 Nov 2013 20:24:46 +0000

 On Wed, Nov 13, 2013 at 03:55:00PM +0000, reinoud@NetBSD.org wrote:
  > diablo# newfs_lfs -b 512k -B 64M /dev/rvnd0a

 What happens if you try to make an ffs volume with 512k blocks?

 -- 
 David A. Holland
 dholland@netbsd.org

From: David Laight <david@l8s.co.uk>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: kern/48378: LFS can't mount FS newfs_lfs created
Date: Thu, 5 Dec 2013 20:57:42 +0000

 On Wed, Nov 13, 2013 at 08:25:00PM +0000, David Holland wrote:
 > The following reply was made to PR kern/48378; it has been noted by GNATS.
 > 
 > From: David Holland <dholland-bugs@netbsd.org>
 > To: gnats-bugs@NetBSD.org
 > Cc: 
 > Subject: Re: kern/48378: LFS can't mount FS newfs_lfs created
 > Date: Wed, 13 Nov 2013 20:24:46 +0000
 > 
 >  On Wed, Nov 13, 2013 at 03:55:00PM +0000, reinoud@NetBSD.org wrote:
 >   > diablo# newfs_lfs -b 512k -B 64M /dev/rvnd0a
 >  
 >  What happens if you try to make an ffs volume with 512k blocks?

 Isn't the max 64k?

 	David

 -- 
 David Laight: david@l8s.co.uk

From: David Holland <dholland-bugs@netbsd.org>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: kern/48378: LFS can't mount FS newfs_lfs created
Date: Fri, 6 Dec 2013 18:14:05 +0000

 On Thu, Dec 05, 2013 at 08:35:01PM +0000, David Laight wrote:
  >  >  On Wed, Nov 13, 2013 at 03:55:00PM +0000, reinoud@NetBSD.org wrote:
  >  >   > diablo# newfs_lfs -b 512k -B 64M /dev/rvnd0a
  >  >  
  >  >  What happens if you try to make an ffs volume with 512k blocks?
  >  
  >  Isn't the max 64k?

 Well yes, that's the point...

 -- 
 David A. Holland
 dholland@netbsd.org

State-Changed-From-To: open->feedback
State-Changed-By: dholland@NetBSD.org
State-Changed-When: Sat, 12 Jul 2014 17:50:23 +0000
State-Changed-Why:
A question was asked...


From: David Holland <dholland-bugs@netbsd.org>
To: gnats-bugs@netbsd.org
Cc: 
Subject: Re: kern/48378: LFS can't mount FS newfs_lfs created
Date: Tue, 21 Oct 2014 16:08:36 +0000

 Not sent to gnats.

    ------
 From: Reinoud Zandijk <reinoud@NetBSD.org>
 To: NetBSD Problem Report DB Administrator <gnats@NetBSD.org>
 Subject: Re: kern/48378: LFS can't mount FS newfs_lfs created
 Date: Tue, 5 Aug 2014 09:40:53 +0200

 Well yes, FFS does complain about the blocksize being bigger than 64k. Even
 though they share a bit of code, is the LFS implementation limiting our
 inability to handle 512k block sizes or is the format limiting us?

 diablo# newfs -b 512k /dev/rwd2a
 newfs: block size `512k' (524288) is greater than the maximum (65536).
 diablo#

 Reinoud

From: David Holland <dholland-bugs@netbsd.org>
To: gnats-bugs@netbsd.org
Cc: 
Subject: Re: kern/48378: LFS can't mount FS newfs_lfs created
Date: Tue, 21 Oct 2014 16:18:16 +0000

 On Tue, 5 Aug 2014 at 09:40:53 +0200, Reinoud Zandijk wrote:
  >  Well yes, FFS does complain about the blocksize being bigger than 64k. Even
  >  though they share a bit of code, is the LFS implementation limiting our
  >  inability to handle 512k block sizes or is the format limiting us?
  >  
  >  diablo# newfs -b 512k /dev/rwd2a
  >  newfs: block size `512k' (524288) is greater than the maximum (65536).
  >  diablo#

 No. The problem is MAXPHYS. You can't mount a volume with block size
 greater than MAXPHYS, either in lfs or ffs or (for now at least) any
 other fs.

 Until the tls-maxphys branch gets merged, that means 64K max. After
 that, you will be able to use more on some devices.

 -- 
 David A. Holland
 dholland@netbsd.org

State-Changed-From-To: feedback->closed
State-Changed-By: dholland@NetBSD.org
State-Changed-When: Mon, 30 May 2016 00:07:28 +0000
State-Changed-Why:
Operator error :-)


>Unformatted:

Home	PR Database Search