lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <CADzUK1LUXH=w+FMxScugv-jW8ECHYmDBOrwT8OpXJdA336XA4g@mail.gmail.com>
Date:	Thu, 7 Feb 2013 11:43:23 -0500
From:	Autif Khan <autif.mlist@...il.com>
To:	linux-ext4@...r.kernel.org
Subject: How can I flush all writes before yanking the power cable?

The standard operating procedure to power down my machine is to switch
it off. To work around this, we use mSATA SSDs (actually we recently
switched from SATA SSDs) with linux on a read only partition.

This works just fine, however, we want to be able to upgrade some
parts of the application. To do this, we have put the application on
/app partition. We mount it read only at start up. When we want to
upgrade the app, we remount read-write sync (mount -o remount,rw,sync
/app) perform the write operations and remount read only.

If we yank the power cable after this, we get file system errors on
the next reboot.

We can display a message to the user telling them that it is safe to
power down the machine.

My question is

1) Is this the right place to discuss this or should I have posted
this in the file systems mailing list?

2) how can we determine that all the writes are flushed? (and this it
is safe to yank the power cable)

3) is there a better way to do this? - for example we may not have to
remount read write sync - and we can force a sync before remounting
read only or something

I have already tried "sudo sync" before remounting the filesystem as
read only. It does not help.

Please advise.

Thanks

Autif
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists