Re: bin/45191: newfs_v7fs(8) doesn't work on a disk partition

[Matthias Scheler <tron%zhadum.org.uk@localhost>]

The following reply was made to PR bin/45191; it has been noted by GNATS.

From: Matthias Scheler <tron%zhadum.org.uk@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: 
Subject: Re: bin/45191: newfs_v7fs(8) doesn't work on a disk partition
Date: Tue, 2 Aug 2011 11:22:00 +0100

 On Mon, Aug 01, 2011 at 06:25:02AM +0000, David Holland wrote:
 > The following reply was made to PR bin/45191; it has been noted by GNATS.
 > 
 > From: David Holland <dholland-bugs%netbsd.org@localhost>
 > To: gnats-bugs%NetBSD.org@localhost
 > Cc: 
 > Subject: Re: bin/45191: newfs_v7fs(8) doesn't work on a disk partition
 > Date: Mon, 1 Aug 2011 06:20:04 +0000
 > 
 >  On Sat, Jul 30, 2011 at 11:30:01AM +0000, tron%zhadum.org.uk@localhost 
 > wrote:
 >   > tron@lyssa:~#newfs_v7fs /dev/rwd1e
 >   > newfs_v7fs: mmap failed. use direct I/O.: Invalid argument
 >   > newfs_v7fs: sector=1
 >   > : Read-only file system
 >   > newfs_v7fs: Can't write back superblock.: Input/output error
 >   > newfs_v7fs: Input/output error
 >  
 >  Is this because it's a partition or because it's too big to mmap?
 >  (Does a 512M partition work?)
 
 It works with a 46.4MB partition:
 
        tron@lyssa:~tron#newfs_v7fs /dev/rwd0e
        newfs_v7fs: mmap failed. use direct I/O.: Invalid argument
 
 I can mount the resulting file-system and write files to it.
 
 >  Of course, mmap'ing disk images is kind of silly...
 
 I would call it optimistic. :-)
 
        Kind regards
 
 -- 
 Matthias Scheler                                  http://zhadum.org.uk/