From owner-freebsd-geom@freebsd.org Thu Sep 7 17:06:32 2017 Return-Path: Delivered-To: freebsd-geom@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2232FE0390E for ; Thu, 7 Sep 2017 17:06:32 +0000 (UTC) (envelope-from hsr.hackspace@gmail.com) Received: from mail-ua0-x22a.google.com (mail-ua0-x22a.google.com [IPv6:2607:f8b0:400c:c08::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 82FAF827AD for ; Thu, 7 Sep 2017 17:06:31 +0000 (UTC) (envelope-from hsr.hackspace@gmail.com) Received: by mail-ua0-x22a.google.com with SMTP id q29so551435uaf.3 for ; Thu, 07 Sep 2017 10:06:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=e6DwaWRe6aQb6kKWaC4s45Rz6Iwxd13wmHONfYbWGnU=; b=XeCbARgT1PGFBheQUhmDquvv6i7QbL4iWDyn0BCA700e0Z2fDf1urosQvl99cy2Qrb KhT9Ue8ZN3oK+OfAcYqNwHslVDm+mFpdPFh5+1MOrUMkgdkhPH6tDKBxTZUp9biJP3m+ PcOMAME7+R7aWv+CB4qsHBEzmGol9SnOXL6tUeDrEVCjsPzEDvQIYbXCD33s2AqIWsq9 UWeiGEer7M6fwsEPEiEj2XhacXimaboOuv1g4itv35ZDIHzybZo3PnarAWmBPNwKS1de Isa6578gRdWxkF74Pi5ggl14qJuViGJkV3QXzPhd6Nvb7mNX0K8+A45m2gkafhmoTdj1 jocQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=e6DwaWRe6aQb6kKWaC4s45Rz6Iwxd13wmHONfYbWGnU=; b=m75D7MzHCP9oZ0OvODG3gCBSuhMYK3R+3/4yoqFVN6e0CMF8unxHJfJ3jHQ6y7YQj7 fRZ+druy1FU9y73tQIGSy03rjXPaj+kGBKEc+2+A+V7cByYIga0Are2MEAlQkozL59vh uQstkrtcYB/jA1t9AJqbZ40g81laCgqOxnm1eFcr0rEI4YE0W5e5NyyY/XJ9QRFv5O/k 5DdXyHRCKx0b4KgAHpV/c4WT+IoJfumFvTwRPGyINHBi5x0IXy6KID7ZT4x8SKpme38k rfzHkehmAQj39dGP6DVAARrNLdQt6LSsAlZS6Mr6AMwC5gGUvIwNmLnteRQ+2bIcqadx niaQ== X-Gm-Message-State: AHPjjUgzhMDmWK4Is1GYvGTEdjtJVKxGR5VAuwaGb0LhsCvC8iuqtlXp xeT9tpHgiLeEILUIXgsypKSOtoWjx9iM X-Google-Smtp-Source: ADKCNb7TD/V2vwOPp/38hLIgUyVEpzGbMdIiA2x+birMIaewkhyJoir/tIQFEdSH28Twe6gUJjp54SGLxWWSTOr+N7E= X-Received: by 10.159.59.17 with SMTP id i17mr2140237uah.165.1504803989857; Thu, 07 Sep 2017 10:06:29 -0700 (PDT) MIME-Version: 1.0 Received: by 10.31.206.6 with HTTP; Thu, 7 Sep 2017 10:06:29 -0700 (PDT) In-Reply-To: References: From: HSR Hackspace Date: Thu, 7 Sep 2017 22:36:29 +0530 Message-ID: Subject: Fwd: EXT2 partitioning in BSD To: freebsd-geom@freebsd.org Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Sep 2017 17:06:32 -0000 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