similar to: how to cleanup old superblock

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,

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

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

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, I am using btrfs for remote backups (via rsync), with daily and weekly snapshots. I see these messages in kern.log: Jul 18 07:09:43 backup1 kernel: [3437126.458374] btrfs: unlinked 9 orphans Jul 18 12:01:01 backup1 kernel: [3454604.905856] btrfs: unlinked 1 orphans Jul 18 13:01:51 backup1 kernel: [3458254.990199] btrfs: unlinked 1 orphans Jul 19 04:01:41 backup1 kernel: [3512244.236347]

Samba4 as AD controller. Same samba as domain members. Winbind. Periodically (once in few days) after subject message in winbind logs its stop working and only restart of winbindd helps. Error message: [2015/08/10 13:31:14.410866, 0] ../source3/libads/sasl.c:1025(ads_sasl_spnego_bind) kinit succeeded but ads_sasl_spnego_krb5_bind failed: The context has expired : Success smb.conf [global]

https://bugzilla.redhat.com/show_bug.cgi?id=907554 In particular comments 2 & 3. We could change libguestfs's guestfs_mkfs (internally) so it always does an implicit wipefs on the filesystem. wipefs is not too onerous -- in particular I believe it only writes to a few chosen areas of the disk. Especially considering that we're about to run mkfs anyway which for some filesystems

Hello all, I recently had a power failure and can no longer mount my /home directory. The harddrive has two BTRFS partitions: sda7(/) and sda8(/home). The / partition loads up just fine, but /home does not. I''ve tried btrfsck as shown below and I''ve included dmesg pertaining to btrfs. This is on ArchLinux and the software versions are as follows: btrfs-progs-unstable

12.08.2015 15:22, Rowland Penny пишет: > On 12/08/15 12:17, Dmitry MiksIr wrote: > > Hi, I think your kerberos ticket is expiring, but don't really know why. > > As Louis as said, you don't need these lines in krb5.conf: > > ticket_lifetime = 24h > renew_lifetime = 7d > Ok, i will try to remove. Lets see. > You also don't need these lines in smb.conf:

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

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

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

Hi, There''s been discussion before on this list on the very small number of hard links supported by btrfs.[1][2] In those threads, an often asked question has been if there''s a real world use case the limit breaks. Also it has been pointed out that a fix for this would need a disk format change. As discussed in bug #15762 [3], there are certainly real-world use cases this

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 +++

- Ahh OK now I see why I was confused. The originally posted partition map uses cylinders as units, not LBA. I missed that. Cylinder 1 is the same as LBA 63. And that is sufficiently large for a GRUB legacy stage 2. - OK this is screwy. Partitions 1 and 3 on both drives have the same number of sectors, but partitions 2 differ: /dev/hde2 401,625 975,691,709 975,290,085 fd Linux

E.g. btrfsctl -r -4000m /dev/sda5 results in: ioctl:: Inappropriate ioctl for device Distribution: Ubuntu 10.10 Kernel: 2.6.35-22-generic According to the Synaptic Package manager, the version of btrfs-tools is 0.19+20100601-3 Other information that can be of interest: - I started Ubuntu on a live CD - before invoking the btrfsctl command I invoked apt-get update. I have googled but have not

I have the attached error from trying to mount btrfs on external hard drive. The F.S. was my primary system, then I dd''d it to an external and reinstalled Fedora. I tried to follow https://btrfs.wiki.kernel.org/index.php/Problem_FAQ#Filesystem_can.27t_be_mounted_by_label. I used "# btrfs device scan --all-devices" before attempting to mount.   What should I do?

Dear fellow CentOS users, I have never experienced this problem with hard disk management before and cannot explain it to myself on any rational basis. The setup: I have a workstation for testing, running latest CentOS 7.3 AMD64. I am evaluating oVirt and a storage-ha as part of my bachelors thesis. I have already been running a RAID1 (mdraid, lvm2) for the system and some oVirt 4.1 testing.

Hello If I want to manage a complete disk with btrfs, what''s the "Best Practice"? Would it be best to create the btrfs filesystem on "/dev/sdb", or would it be better to create just one partition from start to end and then do "mkfs.btrfs /dev/sdb1"? Would the same recomendation hold true, if we''re talking about huge disks, like 4TB or so?