grub-devel.gnu.org archive mirror
 help / color / mirror / Atom feed
From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: BtrFS available in experimental
Date: Fri, 03 Dec 2010 22:02:22 +0100	[thread overview]
Message-ID: <4CF95ADE.6020002@gmail.com> (raw)
In-Reply-To: <4CF7B02F.1020105@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2059 bytes --]

On 12/02/2010 03:41 PM, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
> On 12/01/2010 04:51 PM, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
>   
>> Hello, all. It seems incresingly unpractical to assume that btrfs legal
>> issues will be resolved. So I using this specification :
>> https://btrfs.wiki.kernel.org/index.php/User:Wtachi/On-disk_Format
>> implemented a reader. I haven't used any Oracle code for this. Code is
>> fresh from typing fingers. It may or may not work for. I'm aware of some
>> possibilities the code may hang parsing an incorrect BtrFS. Currently
>> lacking points:
>> - no multidevice
>>     
Done. RAID0, RAID1 and RAID10 are supported. BtrFS doesn't seem to
currently support anything more.
Note that the redundancy of RAID1(0) isn't used and current code just
read the first device. Also on every mount of multi-device btrfs all the
disks are rescanned. A cache is needed.
>> - no symlinks
>>     
Implemented
>> - no encryption, encoding or compressing
>>     
ZLIB is now supported. BtrFS doesn't seem to support anything more.
>> - no prealloc extents (doesn't look like we need them at all)
>> - grub-mkrelpath isn't adjust for /<subvolume>/ prefix
>>
>>   
>>     
> Several bugs fixed.
> grub-mkrelpath adjust for both bindmount and btrfs subvolume mount
>   
As you can see it looks like all current BtrFS features are supported.
Remaining are speed optimisations (e.g. device assignment cache,
buffering,... ), robustness increase (check for faulty trees, oprionally
checksums) and of course testing, debugging and maintaining.
>> The syntax on btrfs is
>> /subvolume/standard_path
>> the root subvolume is named "default"
>>   
>>     
> This part was removed. Unlike in ZFS where subvolumes and directories
> are in different namespaces, in btrfs they share the same. so /default/
> was removed.
>   
>> Due to checksumming save_env doesn't work (same problem as on ZFS)
>> Enjoy
>>
>>   
>>     
>
>   


-- 
Regards
Vladimir 'φ-coder/phcoder' Serbinenko



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 294 bytes --]

      parent reply	other threads:[~2010-12-03 21:02 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-01 15:51 BtrFS available in experimental Vladimir 'φ-coder/phcoder' Serbinenko
2010-12-02 14:41 ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-12-02 21:15   ` Need --divide flag for assembly of startup.S on some platforms Seth Goldberg
2010-12-02 21:29     ` Colin Watson
2010-12-02 21:39       ` Seth Goldberg
2010-12-03  0:53         ` Error building grub-emu (gnulib/progname.c) Seth Goldberg
2010-12-03  1:07           ` Seth Goldberg
2010-12-03  1:20             ` Seth Goldberg
2010-12-03  1:29             ` Another error building grub-emu (gnulib/error.c) Seth Goldberg
2010-12-03  1:39               ` Seth Goldberg
2010-12-02 21:42       ` Need --divide flag for assembly of startup.S on some platforms Vladimir 'φ-coder/phcoder' Serbinenko
2010-12-04 15:47         ` Colin Watson
2010-12-04 16:20           ` Colin Watson
2010-12-03 21:20     ` Need LARGEFILE_SOURCE && _FILE_OFFSET_BITS=64 Seth Goldberg
2010-12-04 15:25       ` Colin Watson
2010-12-06  7:18         ` Seth Goldberg
2010-12-03 21:02   ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4CF95ADE.6020002@gmail.com \
    --to=phcoder@gmail.com \
    --cc=grub-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).