| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Tue, 12 Feb 2008 15:00:20 +0100 (CET) From: Jan Engelhardt <jengelh@...putergmbh.de> To: Chris Mason <chris.mason@...cle.com> cc: David Miller <davem@...emloft.net>, linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org, btrfs-devel@....oracle.com Subject: Re: BTRFS partition usage... On Feb 12 2008 08:49, Chris Mason wrote: >> > >> > This is a real issue on sparc where the default sun disk labels >> > created use an initial partition where block zero aliases the disk >> > label. It took me a few iterations before I figured out why every >> > btrfs make would zero out my disk label :-/ >> >> Actually it seems this is only a problem with mkfs.btrfs, it clears >> out the first 64 4K chunks of the disk for whatever reason. > >It is a good idea to remove supers from other filesystems. I also need to add >zeroing at the end of the device as well. > >Looks like I misread the e2fs zeroing code. It zeros the whole external log >device, and I assumed it also zero'd out the start of the main FS. > >So, if Btrfs starts zeroing at 1k, will that be acceptable for you? Something looks wrong here. Why would btrfs need to zero at all? Superblock at 0, and done. Just like xfs. (Yes, I had xfs on sparc before, so it's not like you NEED the whitespace at the start of a partition.) -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists