AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20080314143258.644bb494@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:onstor-exch02.onstor.net
NSV:
SSH:
R:<eric.barrett@onstor.com>,<paul.hammer@onstor.com>,<larry.scheer@onstor.com>,<john.keiffer@onstor.com>,<dl-fs@onstor.com>,<dl-qa@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	BB375AF679D4A34E9CA8DFA650E2B04E08DF3AEC@onstor-exch02.onstor.net
X-Sylpheed-End-Special-Headers: 1
Date: Fri, 14 Mar 2008 14:33:32 -0700
From: Andrew Sharp <andy.sharp@onstor.com>
To: "Eric Barrett" <eric.barrett@onstor.com>
Cc: "Paul Hammer" <paul.hammer@onstor.com>, "Larry Scheer"
 <larry.scheer@onstor.com>, "John Keiffer" <john.keiffer@onstor.com>,
 "dl-File System" <dl-fs@onstor.com>, "dl-QA" <dl-qa@onstor.com>
Subject: Re: mounting the secondary flash partition
Message-ID: <20080314143332.538bb65a@ripper.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E08DF3AEC@onstor-exch02.onstor.net>
References: <BB375AF679D4A34E9CA8DFA650E2B04E08DF3905@onstor-exch02.onstor.net>
	<BB375AF679D4A34E9CA8DFA650E2B04E056C9494@onstor-exch02.onstor.net>
	<BB375AF679D4A34E9CA8DFA650E2B04E08DF3A6A@onstor-exch02.onstor.net>
	<BB375AF679D4A34E9CA8DFA650E2B04E080CB29C@onstor-exch02.onstor.net>
	<BB375AF679D4A34E9CA8DFA650E2B04E08DF3AEC@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 11:46:32 -0700 "Eric Barrett"
<eric.barrett@onstor.com> wrote:

> I would think it will run automatically any time there's an unexpected
> SSC reboot -- either a Linux kernel oops or a power failure.

Nope.  We're using ext3, it is journaled, and fsck should normally never
be run.

> 
> ________________________________
> 
> From: Paul Hammer 
> Sent: Friday, March 14, 2008 11:05 AM
> To: Eric Barrett; Larry Scheer; John Keiffer; dl-File System; Andy
> Sharp Cc: dl-QA
> Subject: RE: mounting the secondary flash partition
> 
> 
> 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
> 
>  
> 
>  
> 
