On Sat, Sep 08, 2012 at 01:50:26PM +0200, Claus Lensb?l wrote:
> Ok, so I'm trying it out. I got the disk ready with:
> mkfs.ext2 -L "cmol-storage" -m 0 -I 128 /dev/sdb1
> , to get the inodes right according to this:
> http://efreedom.com/Question/H-33983/Flash-Drive-OpenBSD-Specified-Device-Mat
> ch-Mounted-Device
> 
> The disk shows up in dmesg as:
> umass0 at uhub0 port 1 configuration 1 interface 0 "Seagate Backup+ Desk"
> rev 2.10/1.00 addr 2
> umass0: using SCSI over Bulk-Only
> scsibus1 at umass0: 2 targets, initiator 0
> sd0 at scsibus1 targ 1 lun 0: <Seagate, Backup+ Desk, 0503> SCSI4 0/direct
> fixed
> sd0: 2861588MB, 4096 bytes/sec, 732566645 sec total
> 
> And disklabel shows:
> # disklabel
> sd0
> 
> # /dev/rsd0c:
> type: SCSI
> disk: SCSI disk
> label: Backup+ Desk
> duid: 0000000000000000
> flags:
> bytes/sector: 4096
> sectors/track: 63
> tracks/cylinder: 255
> sectors/cylinder: 16065
> cylinders: 45600
> total sectors: 732566645
> boundstart: 0
> boundend: 732566645
> drivedata: 0
> 
> 16 partitions:
> #                size           offset  fstype [fsize bsize  cpg]
>   c:        732566645                0  unused
>   i:        732566272              256  ext2fs
> 
> However, when I'm trying to mount I get:
> # mount -t ext2fs /dev/sd0i /mnt
> mount_ext2fs: /dev/sd0i on /mnt: specified device does not match mounted
> device
> 
> Any ideas?
> 
> On Fri, Sep 7, 2012 at 6:07 PM, Ted Unangst <t...@tedunangst.com> wrote:
> 
> > On Fri, Sep 07, 2012 at 15:11, Claus Lensb?l wrote:
> > > Hi
> > >
> > > I'm trying to figure out the maximum file system size for ext2 on
> > openbsd,
> > > but I can't seem to find it documented anywhere.
> > > Does anybody know if the limitation is the "old" 2TB (as in linux pre
> > > 2.6.17 ish), or 32TB as newer implementations?
> >
> > As far as I know, thats was a limit of the linux kernel, not the
> > filesystem, so it doesn't apply, but I'm not that familiar with ext2fs.
> 

I'm suspicious that the problem lies with:

        bytes/sector: 4096

since there should be no problem handling inodes larger than 128 bytes since
a commit in 2008.

.... Ken

Reply via email to