Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 7 Sep 2017 22:36:29 +0530
From:      HSR Hackspace <hsr.hackspace@gmail.com>
To:        freebsd-geom@freebsd.org
Subject:   Fwd: EXT2 partitioning in BSD
Message-ID:  <CAJN=9WEdaEc%2Bn0RsisssgGYRJ-O15crfury_UGT3JKTFDWv-oA@mail.gmail.com>
In-Reply-To: <CAJN=9WG3eTtKzD3R3P_MotGdda_ywU%2B5OAS=EzD38upHu33OhA@mail.gmail.com>
References:  <CAJN=9WG3eTtKzD3R3P_MotGdda_ywU%2B5OAS=EzD38upHu33OhA@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Hi folks;

I'm writing this mail regarding a strange issue while formatting a
parting as ext2 on a x86
machine running Freebsd 10.1 with MBR partitioning with BSDDISKLABEL
support enabled.

Warning: could not erase sector 0: Operation not permitted or
Warning: could not erase sector 0: Attempt to write block to file
system resulted in short write

If I try to format same partition as UFS. Formatting is clean which I
think proves that HDD (512 byte sectors) is good.

This is not HDD or  kernel issue as in GPT partitioning case I use
same kernel.  Does BSD disk label or MBR partitioning require anything
extra (other
than FS system support)  to be enabled  in kernel?

I have posted more details and logs here:

https://unix.stackexchange.com/questions/390050/creating-a-ext2-partition-on-freebsd-10-1-running-on-x86-based-box-with-mbr-part

Appreciate any help that can guide my debugging for this issue.

TIA
_SP

++++++++++++++++++++++++++++++++++++++++++
pod0226-wsa115:rtestuser 33] ./mkfs.ext2 /dev/mfid0s1a
mke2fs 1.42.10 (18-May-2014)
---------------------------------------------> older version
/dev/mfid0s1a contains a ext3 file system
        created on Sun Sep  3 15:30:47 2017
Proceed anyway? (y,n) y
Creating filesystem with 524288 4k blocks and 131072 inodes
Filesystem UUID: db822d68-307b-47b7-8f60-2ac75cb08504
Superblock backups stored on blocks:
        32768, 98304, 163840, 229376, 294912

Allocating group tables: done
Warning: could not erase sector 0: Attempt to write block to file
system resulted in short write
Writing inode tables: done
Writing superblocks and filesystem accounting information: done

 pod0226-wsa115:rtestuser 18] ./mkfs.ext4 /dev/mfid0s1a
mke2fs 1.43.4 (31-Jan-2017) -------------------->>.latest version
/dev/mfid0s1a contains a ext2 file system
        created on Sun Sep  3 16:09:15 2017
Proceed anyway? (y,N) y
Creating filesystem with 524288 4k blocks and 131072 inodes
Filesystem UUID: 7a320b3e-6a61-44df-9947-8abe12b05194
Superblock backups stored on blocks:
        32768, 98304, 163840, 229376, 294912

Allocating group tables: done
Warning: could not erase sector 0: Operation not permitted -------->
Writing inode tables: done
Creating journal (16384 blocks): done
Writing superblocks and filesystem accounting information: done

pod0226-wsa115:rtestuser 21] df -h
Filesystem       Size    Used   Avail Capacity  Mounted on
/dev/mfid0s1d    1.9G    575M    1.2G    31%    /
devfs            1.0K    1.0K      0B   100%    /dev
/dev/mfid0s1e    374M     20M    325M     6%    /var
/dev/mfid0s1g    789G     62G    664G     9%    /data
/dev/mfid0s1h    1.9G     41K    1.8G     0%    /var/db/godspeed
procfs           4.0K    4.0K      0B   100%    /proc
linprocfs        4.0K    4.0K      0B   100%    /compat/linux/proc
linsysfs         4.0K    4.0K      0B   100%    /compat/linux/sys
pod0226-wsa115:rtestuser 22]


More logs are here :
https://unix.stackexchange.com/questions/390050/creating-a-ext2-partition-on-freebsd-10-1-running-on-x86-based-box-with-mbr-part



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJN=9WEdaEc%2Bn0RsisssgGYRJ-O15crfury_UGT3JKTFDWv-oA>