From mboxrd@z Thu Jan 1 00:00:00 1970 From: Edward Shishkin Subject: Re: Reiser4 inclusion into staging tree Date: Sun, 02 Nov 2014 23:47:03 +0100 Message-ID: <5456B467.4080009@gmail.com> References: <5456ADE2.9060405@gmail.com> Mime-Version: 1.0 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=LXhHf//rupfaR/zsROro1GP0IkrNSnYczj8+ErDN0uo=; b=CUzVolVQEFJit877XBbJato3iGsg9J1loH5kgVtu4TpigDTTJgJ4CpibrO1NIZdYUV vojneq2/X+RfeO/Fdo+aFEQi54yk92pSCzd+s872JBEtJR5TFsXcfJI3m3SLeClXtri+ RPfFMQuICgz/5VrYEu6vGNB5PWNkK26s2v+pWKMK/yblo+kyq+Fg/0K+oSbYhjc4znoY PxMggtgCTSqobQRpInpuw8tRqfBIBgd+BH04A4714ONwJa1wdilPka9g6cCGYvkWZkO6 oD7Lpks9IZ2ST9gpgrsBcXcYuWMUO8Vl/fMkHgdws6Sk2ksieGykO/tz6ot3yRvetO5M rKrA== In-Reply-To: <5456ADE2.9060405@gmail.com> Sender: reiserfs-devel-owner@vger.kernel.org List-ID: Content-Type: text/plain; charset="utf-8"; format="flowed" To: =?UTF-8?B?RHXFoWFuIMSMb2xpxIc=?= , reiserfs-devel , Ivan Shapovalov On 11/02/2014 11:19 PM, Edward Shishkin wrote: > > On 11/02/2014 10:09 AM, Du=C5=A1an =C4=8Coli=C4=87 wrote: >> I've made a poll on forums.gentoo.org with a question:" What Reiser4 >> needs for you to start using it?" and with these offered answers I g= ot >> following results: >> >> http://forums.gentoo.org/viewtopic-t-1002726-postdays-0-postorder-as= c-start-25.html=20 >> >> >> Mainline inclusion >> 45% >> Encryption >> 0% >> Snapshots >> 0% >> Defrag >> 0% >> Performance >> 0% >> Subvolumes >> 0% >> Grub2 support >> 0% >> Something else >> 31% >> It's already perfect >> 4% >> I'd never use it >> 18% >> >> >> Something else were users that asked for checksums (we do that for >> ccreg40 partitions or files? > > > Currently a checksum (adler32) is appended at the end of compressed > logical cluster. If cluster is not compressed for some reasons, then > checksum is not appended. > > Also we protect bitmap blocks by checksums. > > >> what about reg40? just sizes AFAIK?), > > > Data of files managed by unix-file plugin is not protected by checksu= ms. > > I think that data protection by checksums is a business of applicatio= ns > (not of the file system). Well, it makes sense, if we support mirroring at the file level. If check is failed, then look at the respective extent in the file-repl= ica. Edward. > > It makes sense to protect formatted nodes of the storage tree. > We'll need a new node format (node41, or so), which includes a 32-bit > checksum, which is updated/checked at flush/jload time. If jload() fi= nds > that check is not OK, then make the file system read-only and suggest > to fsck. > > Edward. > > >> SSD >> support, fixing undeletable dir bug, long mount times (if the large >> partition is / does dont_load_bitmap have to be in boot options or i= t >> can be in /etc/fstab?)... >> >> Based on these results (even on a small portion of linux user base >> that's traditionally been positive about reiser4) I really think tha= t >> taking Reiser4 to the staging tree could be the move that would show >> users that the R4 development has some goal and is not dying down an= d >> with that would come influx of new users/developers. >> >> Ofc this is just my wish as I don't have the knowlege or right to pu= sh >> it to staging but if there's anything you can think of that I can do >> to help (I have one extra machine just waiting for some R4 testing) >> please tell me. >> >> Thanks a lot for your great work >> >> Dushan > -- To unsubscribe from this list: send the line "unsubscribe reiserfs-deve= l" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html