Linux on 390 Port <[email protected]> wrote on 25.07.2006 11:10:04:
> > Carsten Otte wrote: > >> Wrong. Due to caching, as correctly described by David Boyes, the > >> system may change on-disk content even when the application is not > >> running. Example: the syslogd generates a "mark" every 20 minutes. > > John Summerfied wrote: > > syslogd's mark message has nothing to do with caching. > > > > According to its man page, "sync forces changed blocks to disk, updates > > the super block." > > > > If you don't believe (or trust) that, then "mount -o remount" is your > > friend. > You missed my point: From the file system perspective, a snapshot of > an ext3 is _always_ consistent. No need to do remount, sync, shutdown > of application or shutdown of the entire system. > Whether the file system is consistent in itself after a restart is irrelevant form an application perspective if the application has e.g. state that is independent from the file system content. You can only capture that by application collaboration or by forcing that state to be hardened on persistent storage, hence shutting down the application prior to backup/archive. > regards, > Carsten > > ---------------------------------------------------------------------- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 Ingo -- Ingo Adlung, STSM, System z Linux and Virtualization Architecture mail: [EMAIL PROTECTED] - phone: +49-7031-16-4263 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
