Here's a little more info regarding the file system in question...you'll
notice
the last write time below is 5 minutes ago, but the last mount time was
when the machine was booted?
Can somebody explain that? How can the FS have been written to without
being mounted?
root# tune2fs -l /dev/hda1
tune2fs 1.41.3 (12-Oct-2008)
Filesystem volume name: ROOT_FS
Last mounted on: <not available>
Filesystem UUID: 995744b8-7193-4799-b40d-89c265dcf07a
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: ext_attr resize_inode dir_index filetype
sparse_super large_file
Filesystem flags: signed_directory_hash
Default mount options: (none)
Filesystem state: not clean
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 232928
Block count: 931384
Reserved block count: 9313
Free blocks: 764434
Free inodes: 201548
First block: 0
Block size: 4096
Fragment size: 4096
Reserved GDT blocks: 227
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 8032
Inode blocks per group: 502
Filesystem created: Thu Apr 21 11:17:14 2011
Last mount time: Fri Apr 22 14:52:56 2011
Last write time: Mon Apr 25 15:46:24 2011
Mount count: 1281
Maximum mount count: -1
Last checked: Thu Apr 21 11:17:14 2011
Check interval: 15552000 (6 months)
Next check after: Tue Oct 18 11:17:14 2011
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 256
Required extra isize: 28
Desired extra isize: 28
Default directory hash: half_md4
Directory Hash Seed: 8d3fd677-c542-4a98-9e93-f1c288036231
On 04/25/2011 03:41 PM, Jeff Ramin wrote:
Thanks for the suggestion, but mounting w/ the noatime option doesn't
affect the behavior.
Anybody else have an idea?
On 04/25/2011 03:03 PM, Michael Steinmann wrote:
hi,
maybe changing relatime to noatime could help?
see
http://linux.koolsolutions.com/2009/01/30/installing-linux-on-usb-part-4-noatime-and-relatime-mount-options/
:
*
2. noatime* – This option stops recording the last file access time
when the file is just read. The /noatime/ option eliminates all the
writes to the disk each time a file was just read which previously
used to happen with /atime/. However a write is made to a disk in
case if a file is being changed/written.
cheers,
michael
2011/4/25 Jeff Ramin <[email protected]
<mailto:[email protected]>>
Hi folks.
I have since switched to ext2 since my original message below,
yet I am
still seeing the same behavior - / is being remounted every 5
minutes. I want
to avoid this, to save wear & tear on the compact flash card.
Nothing in cron would be causing this...any ideas? I'm running
voyage 0.6.5,
and the file system is mounted thus (ouput from mount command):
/dev/disk/by-label/ROOT_FS / ext2 ro,relatime,errors=continue 0 0
Thanks.
---------- Forwarded message ----------
From: Gustin Johnson <[hidden email]
<http://voyage-linux.34677.n3.nabble.com/user/SendEmail.jtp?type=node&node=2661075&i=0&by-user=t>>
Date: Thu, Mar 10, 2011 at 9:17 AM
Subject: Re: [*Voyage*-linux] root being
remounted*every**5**minutes*?
To: Jeff Ramin <[hidden email]
<http://voyage-linux.34677.n3.nabble.com/user/SendEmail.jtp?type=node&node=2661075&i=1&by-user=t>>
My first guess is that writing to the journal on EXT3 requires the FS
to be writable. We use EXT2 on all of our flash based media to
minimize the number of writes.
We once had a similar issue but it was an incorrectly formatted cron
entry. We have a custom script that remounts the FS as writable,
then
does an aptitude update, package download, and simulates an install,
then emails the results. The error in crontab caused this to be run
*every**5**minutes*instead of once a day.
On Thu, Mar 10, 2011 at 7:47 AM, Jeff Ramin <[hidden email]
<http://voyage-linux.34677.n3.nabble.com/user/SendEmail.jtp?type=node&node=2661075&i=2&by-user=t>>
wrote:
>
> I have*voyage*0.6.*5*running on an Alix board, and I'm seeing / get
> remounted*every**5**minutes*, like so:
>
> Mar 10 08:10:*54*singlewire*vmunix*: [603042.739714] EXT3 FS on
hda1, internal
> journal
> Mar 10 08:15:*56*singlewire*vmunix*: [603344.099594] EXT3 FS on
hda1, internal
> journal
> Mar 10 08:21:06 singlewire*vmunix*: [603653.940611] EXT3 FS on
hda1, internal
--
Jeff Ramin
Software Engineer
Singlewire Software
2601 W Beltline Hwy #510
Madison, WI 53713
Phone Direct - 608.661.1172
www.singlewire.com <http://www.singlewire.com>
_______________________________________________
Voyage-linux mailing list
[email protected] <mailto:[email protected]>
http://list.voyage.hk/mailman/listinfo/voyage-linux
--
Jeff Ramin
Software Engineer
Singlewire Software
2601 W Beltline Hwy #510
Madison, WI 53713
Phone Direct - 608.661.1172
www.singlewire.com
--
Jeff Ramin
Software Engineer
Singlewire Software
2601 W Beltline Hwy #510
Madison, WI 53713
Phone Direct - 608.661.1172
www.singlewire.com
_______________________________________________
Voyage-linux mailing list
[email protected]
http://list.voyage.hk/mailman/listinfo/voyage-linux
