From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Mason Subject: Re: Problems with journal size option on mkfs Date: 15 May 2002 19:43:54 -0400 Message-ID: <1021506234.16648.754.camel@tiny> References: Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: list-help: list-unsubscribe: list-post: In-Reply-To: List-Id: Content-Type: text/plain; charset="us-ascii" To: Steve Pratt Cc: reiserfs-list@namesys.com On Wed, 2002-05-15 at 17:49, Steve Pratt wrote: > > Chris Mason wrote: > >On Wed, 2002-05-15 at 16:12, Steve Pratt wrote: > >> > >> I am in the process of writing a File System Interface Module (FSIM) for > >> EVMS that will interface with ReiserFS and am having a problem with the > -s > >> (journal size) option on mkfs.reiserfs. The problem is that if I > specify > >> any journal size the mkfs fails. By fails, what I mean is that the > device > >> is not mountable, I don't actually get any error message from mkfs. > This > >> happens even when I give it the default size of 8193 blocks. I didn't > see > >> anything in the faq about this option not working, but I tried it on 2 > >> different machines with the same results. I am running tools level > 3.x.1b > >> and stock 2.4.17 kernel + EVMS + JFS + kgdb + vfslock. > >> > >> Here is a sample of the output, the only line that changes is the > reference > >> to non-standard journal > > >The kernel side of the dedicated logging device code has not been sent > >for inclusion in 2.4.x yet. The beta patch below implements it, against > >2.4.19-pre7. > > So the -s option only works with offline log devices? It doesn't say > anything about this in the man pages. Also, wouldn't the mkfs code just > ignore this option if you did not specify an external log device (like the > example)? > > Just looked at man page again, and it indicates that this should work for > inline logs as well. > It works with both, but the kernel doesn't understand things properly without the patch. -chris