AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20080314144148.4cf510dc@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:onstor-exch02.onstor.net
NSV:
SSH:
R:<sandrine.boulanger@onstor.com>
MAID:1
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
RMID:#imap/andys@onstor.net@onstor-exch02.onstor.net/INBOX	0	BB375AF679D4A34E9CA8DFA650E2B04E05C744D6@onstor-exch02.onstor.net
X-Sylpheed-End-Special-Headers: 1
Date: Fri, 14 Mar 2008 14:42:01 -0700
From: Andrew Sharp <andy.sharp@onstor.com>
To: "Sandrine Boulanger" <sandrine.boulanger@onstor.com>
Subject: Re: mounting the secondary flash partition
Message-ID: <20080314144201.03ce3ab4@ripper.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E05C744D6@onstor-exch02.onstor.net>
References: <20080314143238.380b2f18@ripper.onstor.net>
	<BB375AF679D4A34E9CA8DFA650E2B04E05C744D6@onstor-exch02.onstor.net>
Organization: Onstor
X-Mailer: Sylpheed-Claws 2.6.0 (GTK+ 2.8.20; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

On Fri, 14 Mar 2008 14:36:02 -0700 "Sandrine Boulanger"
<sandrine.boulanger@onstor.com> wrote:

> It runs by itself on my machine after power failures sometimes. That's
> what hppens on bsd flashes. The filer crashes (unfortunately too
> often), and sometimes when it boots, fsck runs and delete files.
> We've seen too many times in QA but nobody could ever find a
> resolution for this. We'll do similar test with Linux: keep crashing
> FP and see how the fs on flash does at reboot.

I thought we'd been doing that test these last many weeks whether we
wanted to or not ~:^)

The theory is that ext3 being jounaled and whatnot will make it
significantly more resistant to corruptions that occur do to unforseen
crashes.  Like our own filesystem, only better ~:^)

> -----Original Message-----
> From: Andy Sharp 
> Sent: Friday, March 14, 2008 2:33 PM
> To: Paul Hammer
> Cc: Eric Barrett; Larry Scheer; John Keiffer; dl-File System; dl-QA
> Subject: Re: mounting the secondary flash partition
> 
> On OpenBSD, fsck is demonized, but the real problem is the filesystem
> is corrupt.  fsck is just doing its job.
> 
> On Linux, it's a completely different situation and I don't expect
> that fsck should normally ever be used unless something seriously bad
> is wrong with the filesystem on the flash, in which case it should
> probably be initialized anyway.  In the field I expect this to be so
> rare as to be never seen.  Put it this way: how many engineers here at
> Onstor have had to run fsck on their workstations?  Except for Jim,
> I'm guessing damn close to zero  ~:^)
> 
> On Fri, 14 Mar 2008 11:05:22 -0700 "Paul Hammer"
> <paul.hammer@onstor.com> wrote:
> 
> > Are there any instances where 2efsck will run automatically? 
> >  
> > Want to know if we think we are going to see the same type of
> > failures in the field that we see today when on the bobcat flash
> > fsck blows away files. Thanks,
> >  
> > -Paul
> > 
> > ________________________________
> > 
> > From: Eric Barrett
> > Sent: Fri 3/14/2008 10:58 AM
> > To: Larry Scheer; John Keiffer; dl-File System; Andy Sharp
> > Cc: dl-QA
> > Subject: RE: mounting the secondary flash partition
> > 
> > 
> > We should fix this before Cougar ships, maybe with the tune2fs
> > command Raj linked.  We have lots of Linux-savvy customers and they
> > will see this when they poke around, and open support cases on it.
> > ("How do I run e2fsck on the flash?"  "Why aren't you fscking your
> > flash regularly?"  Etc.) 
> > 
> > ________________________________
> > 
> > From: Larry Scheer 
> > Sent: Friday, March 14, 2008 10:55 AM
> > To: John Keiffer; dl-File System; Andy Sharp
> > Cc: dl-QA
> > Subject: RE: mounting the secondary flash partition
> > 
> > 
> > 
> > John, 
> > 
> >    This is just the behavior of the ext3 file system used in Linux.
> > After a certain number of reboots this message appears. It is ok to
> > ignore this message.
> > 
> >  
> > 
> > Andy might have more to say about it.
> > 
> >  
> > 
> > Larry
> > 
> >  
> > 
> > ________________________________
> > 
> > From: John Keiffer 
> > Sent: Friday, March 14, 2008 8:27 AM
> > To: Larry Scheer; dl-File System
> > Cc: dl-QA
> > Subject: mounting the secondary flash partition
> > 
> >  
> > 
> > I notice the following 4 lines when I mount the secondary flash's
> > root partition. Are these normal and expected (the second one seems
> > the most concerning)?
> > 
> >  
> > 
> > Mar 14 08:21:01 g6r10 kernel: kjournald starting.  Commit interval 5
> > seconds
> > 
> > Mar 14 08:21:01 g6r10 kernel: EXT3-fs warning: maximal mount count
> > reached, running e2fsck is recommended
> > 
> > Mar 14 08:21:01 g6r10 kernel: EXT3 FS on sda1, internal journal
> > 
> > Mar 14 08:21:01 g6r10 kernel: EXT3-fs: mounted filesystem with
> > ordered data mode.
> > 
> >  
> > 
> > Thank you,
> > 
> > John Keiffer
> > 
> >  
> > 
> >  
> > 
