linux-kernel - Re: [ANNOUNCE] Btrfs v0.13

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <200804011158.37620.chris.mason@oracle.com>
Date:	Tue, 1 Apr 2008 11:58:37 -0400
From:	Chris Mason <chris.mason@...cle.com>
To:	Alex Chiang <achiang@...com>
Cc:	David Miller <davem@...emloft.net>, linux-kernel@...r.kernel.org,
	linux-fsdevel@...r.kernel.org, btrfs-devel@....oracle.com
Subject: Re: [ANNOUNCE] Btrfs v0.13

On Monday 31 March 2008, Alex Chiang wrote:
> * David Miller <davem@...emloft.net>:
> > From: Alex Chiang <achiang@...com>
> > Date: Mon, 31 Mar 2008 14:26:33 -0600
> >
> > > I've gotten as far as successfully creating a btrfs filesystem
> > > (at least that's what btrfsck tells me), but haven't been able to
> > > mount it yet, probably because of the sector size issue.
> >
> > You should be able to make a filesystem with a sector
> > size >= PAGE_SIZE and it should work just fine.  Please
> > give it a try.
>
> Hrm, I'm having issues still. First, here's a patch for
> mkfs.btrfs to allow the user to pass in a different sector size.

I did this a little differently, switching to getopt_long in mkfs.btrfs and 
using [-s | --sectorsize ] for sectorsize.  -s used to be stripesize, but 
that needs to be redone for the multi-device code anyway.

You can pull down integrated versions of your patches from:

http://www.kernel.org/hg/btrfs/kernel-unstable
http://www.kernel.org/hg/btrfs/progs-unstable

Make sure to update both, there are minor format changes hidden in the 
unstable tree since you last used it.

-chris
--
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/