Re: another ext3 question
Hi, Sorry for the delay, I've been on holiday for a couple of weeks. On Thu, Jul 27, 2000 at 07:36:34PM -0400, Jeremy Hansen wrote: > > ok ... to clarify ... ext3 _guarantees_ consistent file system metadata > or empirically, it tends to be robust about maintaining consistent > file system metadata across abrupt reboots? It guarantees it --- all fs data (including things like quota data) are guaranteed consistent across reboots without fsck. --Stephen
Re: another ext3 question
I actually heard this quite some time ago and I always use it in any example where people are already using ext3 in a production environment. Are there more cases of ext3 in production? Someone asked this question: ok ... to clarify ... ext3 _guarantees_ consistent file system metadata or empirically, it tends to be robust about maintaining consistent file system metadata across abrupt reboots? reiserfs, jfs, etc. all _guarantee_ this condition. So I'm really not sure what this means because I thought the *point* of a journalling filesystem was the above question. Thanks -jeremy > On Thu, Jul 27, 2000 at 01:41:54PM -0400, Jeremy Hansen wrote: > > We're really itching to use ext3 in a production environment. Can you > > give any clues on how things are going? I'm not asking for time frames by > > any means but rather like, yes, things are coming along nicely or whatever > > clues you can give. > > the rpmfind.net and fr.rpmfind.net servers have been running completely > on top of ext3 for more than one year without troubles. I use it for a > couple of W3C servers too. > > Daniel > > -- http://www.xxedgexx.com | [EMAIL PROTECTED] -
Re: another ext3 question
On Thu, Jul 27, 2000 at 01:41:54PM -0400, Jeremy Hansen wrote: > We're really itching to use ext3 in a production environment. Can you > give any clues on how things are going? I'm not asking for time frames by > any means but rather like, yes, things are coming along nicely or whatever > clues you can give. the rpmfind.net and fr.rpmfind.net servers have been running completely on top of ext3 for more than one year without troubles. I use it for a couple of W3C servers too. Daniel -- [EMAIL PROTECTED] | W3C, INRIA Rhone-Alpes | Today's Bookmarks : Tel : +33 476 615 257 | 655, avenue de l'Europe | Linux XML libxml WWW Fax : +33 476 615 207 | 38330 Montbonnot FRANCE | Gnome rpm2html rpmfind http://www.w3.org/People/all#veillard%40w3.org | RPM badminton Kaffe
Re: another ext3 question
Hi, On Thu, Jul 27, 2000 at 01:41:54PM -0400, Jeremy Hansen wrote: > > We're really itching to use ext3 in a production environment. Can you > give any clues on how things are going? The ext3-0.0.2f appears to be rock solid. Andreas has got prototyped code for e2fsck log replay, and I've got pending code for out-of-memory and IO failures sitting here, along with most of the code for metadata-only journaling. I'm off on holiday in a few hours for 2 weeks, but expect a release shortly after I get back with some more goodies in it. Cheers, Stephen
Re: another ext3 question
Thanks! I've been using ext3 on about 5 machines for the past week or so and it's been great so far. Haven't had any problems except for that weird thing creating that journal on the root filesystem and it was getting confused witht he ramdisk or whatever, but making a boot disk and mounting fixed that. We're really itching to use ext3 in a production environment. Can you give any clues on how things are going? I'm not asking for time frames by any means but rather like, yes, things are coming along nicely or whatever clues you can give. Also, do you know of anyone creating an anaconda install that will take advantage of ext3? Assuming I would know anaconda which I don't, it would seem easy enough to create journal files just based on the size of partition. That would be swell. Thanks -jeremy > Hi, > > On Fri, Jul 21, 2000 at 11:54:20PM -0600, Andreas Dilger wrote: > > > Note that you should not make the journals so large that they are a > > major fraction of your RAM, as you will not gain anything by this. > > A few megabytes is fine, 1024 disk blocks is the minimum. > > Yep. The main drawbacks to a large journal is that (a) they can pin a > lot of buffers in memory at once, and (b) they take longer to recover. > The only advantage of a large journal is that it gives the filesystem > more flexibility in writing things back to the main disk, but it's not > a large effect unless you have a very heavy write load. > > Cheers, > Stephen > -- http://www.xxedgexx.com | [EMAIL PROTECTED] -
Re: another ext3 question
Hi, On Fri, Jul 21, 2000 at 11:54:20PM -0600, Andreas Dilger wrote: > Note that you should not make the journals so large that they are a > major fraction of your RAM, as you will not gain anything by this. > A few megabytes is fine, 1024 disk blocks is the minimum. Yep. The main drawbacks to a large journal is that (a) they can pin a lot of buffers in memory at once, and (b) they take longer to recover. The only advantage of a large journal is that it gives the filesystem more flexibility in writing things back to the main disk, but it's not a large effect unless you have a very heavy write load. Cheers, Stephen
Re: another ext3 question
Jeremy writes: > So I setup ext3 on my root partition on my laptop. Now I have another > partition in /boot. Do I need to create a journal file for each > partition? Or do I just point it to the journal file I created for my > root partition. You currently need to have 1 journal file for each filesystem. In the future, it will be possible to have multiple filesystems share the same journal. Note that you should not make the journals so large that they are a major fraction of your RAM, as you will not gain anything by this. A few megabytes is fine, 1024 disk blocks is the minimum. Cheers, Andreas -- Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto, \ would they cancel out, leaving him still hungry?" http://www-mddsp.enel.ucalgary.ca/People/adilger/ -- Dogbert
another ext3 question
So I setup ext3 on my root partition on my laptop. Now I have another partition in /boot. Do I need to create a journal file for each partition? Or do I just point it to the journal file I created for my root partition. I'm guessing the first, but I thought I'd ask cause although I understand that ext3 is in development and there's no guarantees, etc, but I'd like to avoid it if possible. Btw, what I have setup was very easy and seems to work very well. -jeremy -- http://www.xxedgexx.com | [EMAIL PROTECTED] -
