similar to: Should we always do wipefs before mkfs? Discuss ...

Hi Rich: This is a alternative patch, if you like the api name called wipefs ;-P Thanks -Wanlong Gao Wanlong Gao (2): NEW API: add a new api wipefs virt-format: erase the filesystem signatures before erase partitions TODO | 2 -- daemon/zero.c | 17 +++++++++++++++++ format/format.c | 19 ++++---------------

Hi Rich: This is a latest patch. ;-P Comments? Thanks -Wanlong Gao Wanlong Gao (2): NEW API: add a new api wipefs virt-format: erase the filesystem signatures before erase partitions TODO | 2 -- daemon/zero.c | 17 +++++++++++++++++ format/format.c | 19 ++++--------------- generator/generator_actions.ml | 14

we wipe the filesystem signatures from device before do mkfs, since we can't trust mkfs can remove the filesystem signature absolutely. Signed-off-by: Wanlong Gao <gaowanlong at cn.fujitsu.com> --- daemon/mkfs.c | 9 +++++++++ 1 files changed, 9 insertions(+), 0 deletions(-) diff --git a/daemon/mkfs.c b/daemon/mkfs.c index 5475582..19224ec 100644 --- a/daemon/mkfs.c +++

My wipefs has no --force option, as a result mke2fs command in guestfish fails. Looks like 72dd398679cd0bb803daf306d12558369615ba70 needs an adjustment to make use of do_wipefs? Also str_wipefs is not used in that file. Olaf

On Sun, Jan 19, 2014 at 07:42:58PM +0100, Olaf Hering wrote: > My wipefs has no --force option, as a result mke2fs command in guestfish fails. > > Looks like 72dd398679cd0bb803daf306d12558369615ba70 needs an adjustment > to make use of do_wipefs? > Also str_wipefs is not used in that file. Also daemon/zero.c has a wipefs_has_force_option function. It seems like it would be better

Hi, I have a box with / and /home being subvolumes from the same btrfs filesystem. /etc/fstab: UUID=c0686... / btrfs subvol=root,x-systemd.device-timeout=0 1 1 UUID=c0686... /home btrfs subvol=home,x-systemd.device-timeout=0 1 1 ... / is initially mounted readonly by the initramfs, and then after switching to the real system, /home is attempted to be mounted in parallel with /

I''ve filed this bug under util-linux, because I think wipefs isn''t deleting all btrfs metadata it could. But ultimately it appears to be a btrfs bug because nothing else sees the stale volume. https://bugzilla.redhat.com/show_bug.cgi?id=889888#c15 btrfs-progs-0.20.rc1.20121017git92d9eec-1.fc18.x86_64 e2fs-progs-1.42.5-1.fc18.x86_64 kernel 3.7.1-2 Brand new 80GB virtual disk,

Add the new api zero_fs to erase the filesystem signatures on a device but now erase any data. Signed-off-by: Wanlong Gao <gaowanlong at cn.fujitsu.com> --- daemon/zero.c | 17 +++++++++++++++++ generator/generator_actions.ml | 14 ++++++++++++++ src/MAX_PROC_NR | 2 +- 3 files changed, 32 insertions(+), 1 deletions(-) diff --git a/daemon/zero.c

Our code is not ready to cope with a sectorsize that''s not equal to PAGE_SIZE. It will lead to hanging-on while writing something. Signed-off-by: Liu Bo <liubo2009@cn.fujitsu.com> --- fs/btrfs/disk-io.c | 6 +++--- 1 files changed, 3 insertions(+), 3 deletions(-) diff --git a/fs/btrfs/disk-io.c b/fs/btrfs/disk-io.c index 20196f4..b9866f2 100644 --- a/fs/btrfs/disk-io.c +++

If specified, pass the label for the new filesystem directly to the mkfs (or mkfs_btrfs) call. This saves one set_label call, mostly. --- format/format.c | 10 ++++++---- make-fs/make-fs.c | 28 +++++++++++++++++----------- 2 files changed, 23 insertions(+), 15 deletions(-) diff --git a/format/format.c b/format/format.c index 4e6069f..cc371ab 100644 --- a/format/format.c +++ b/format/format.c

On Sun, Jan 19, Richard W.M. Jones wrote: > How about the attached patch (only compile-tested)? This patch works for me. Thanks. Olaf

Hi, I have a test system that booted fine using "Legacy Bios? mode and using the following Kickstart snippet configured the disks correctly:- # Clear the Master Boot Record zerombr # Partition clearing information clearpart --all --initlabel # Disk partitioning information part raid.01 --fstype="raid" --ondisk=sda --size=500 part raid.02 --fstype="raid" --grow

On 08/19/2016 11:35 PM, Phil Manuel wrote: > The install fails under UEFi due to the fact the partitions are not cleared, and it doesn?t have any space to continue. Is there an extra step I need to do to remove the original partitions before the new layout will work ? Yes. If you have pre-existing RAID partitions, they'll automatically assemble before Anaconda runs, and the installer

On Sun, 21 Aug 2016 at 12:51 Gordon Messmer <gordon.messmer at gmail.com> wrote: > On 08/19/2016 11:35 PM, Phil Manuel wrote: > > The install fails under UEFi due to the fact the partitions are not > cleared, and it doesn?t have any space to continue. Is there an extra step > I need to do to remove the original partitions before the new layout will > work ? > > >

On Wed, Sep 29, 2010 at 05:28:33PM +0200, Karel Zak wrote: > On Wed, Sep 29, 2010 at 02:55:59PM +0100, Richard W.M. Jones wrote: > > On Wed, Sep 29, 2010 at 11:11:48AM +0200, Karel Zak wrote: > > > On Sun, Sep 26, 2010 at 05:42:21PM +0100, Richard W.M. Jones wrote: > > > > In any case I'll probably write a small utility which just zaps the > > > >

Add the 'label' optional argument to the mkfs action, so it is possible to set a filesystem label direct when creating it. There may be filesystems not supporting changing the label of existing filesystems but only setting it at creation time, so this new optarg will help. Implement it for the most common filesystems (ext*, fat, ntfs, btrfs, xfs), giving an error for all the others, just

Btrfs has been broken for me for ages. I first reported it on this list 5 months ago[1]. Below is a very simple reproducer that anyone can run. *NB* before you run this, adjust /dev/sda & /dev/sda1 to point to an unused block device! ---------------------------------------------------------------------- #!/bin/sh - set -e while true; do parted -s -- /dev/sda mklabel msdos parted -s --

Folks I've encountered situations where I want to reuse a hard-drive. I do not want to preserve anything on the drive, and I'm not concerned about 'securely erasing' old content. I just want to be able to define it as an Physical Volume (in a logical volume set), or make it a ZFS disk, or sometimes make it a simple EXT3, ExFAT or NTFS disk. However, old

Hello! Long time ago I created btrfs on /dev/sda After some changes btrfs moved to /dev/sda1 (well, to md, and sda1 is part of md). As result, <btrfs fi show> show me 2 filesystems: new one and old one. Probably I need to do some cleaning. Can someone tell me what to do. fdisk -u -c -l /dev/sda Disk /dev/sda: 2000.4 GB, 2000398934016 bytes 81 heads, 63 sectors/track, 765633 cylinders,

On Wed, Jul 23, 2008 at 11:24:49AM +0200, Karel Zak wrote: > On Wed, Jul 23, 2008 at 04:43:30AM -0400, Christoph Hellwig wrote: > > On Wed, Jul 23, 2008 at 10:39:38AM +0200, maximilian attems wrote: > > > klibc mount has only short options thus uses the following syntax > > Frankly, it seems like a klibc problem... well not directly, but right klibc-utils should have