| To: | Subranshu Patel <spatel.ml@xxxxxxxxx> |
|---|---|
| Subject: | Re: Xfs_repair and journalling |
| From: | Matthias Schniedermeyer <ms@xxxxxxx> |
| Date: | Sun, 17 Mar 2013 16:18:41 +0100 |
| Cc: | stan@xxxxxxxxxxxxxxxxx, xfs@xxxxxxxxxxx |
| Delivered-to: | xfs@xxxxxxxxxxx |
| In-reply-to: | <CAEUQceie41dh7h6uZSMu4-JB_BDu82X5CrKxHb=9wVQVAPzKgQ@xxxxxxxxxxxxxx> |
| References: | <CAEUQceh-Xcabr0KErxF6EAdafDDP1PY_AeHwgYB82QeUdyGp-g@xxxxxxxxxxxxxx> <51455408.4070801@xxxxxxxxxxxxxxxxx> <CAEUQceie41dh7h6uZSMu4-JB_BDu82X5CrKxHb=9wVQVAPzKgQ@xxxxxxxxxxxxxx> |
| User-agent: | Mutt/1.5.21 (2010-09-15) |
On 17.03.2013 17:12, Subranshu Patel wrote: > > In case of EXT4, journal will not be replayed on performing mount. One need > to invoke fsck which performs journal playback and then other corruption > checks/recovery. > Correct me if I am wrong. Wrong. ALL Journaling FSes automatically replay the long upon mounting, or at least i don't know of any that don't. Only if there is additional corruption the corresponding fsck comes into play. For XFS i have only needed xfs_repair 1 time in over 10 years (and countless power-failures/spontanous resets, forgotten umounts (USB-drives) ...) and that was caused by a bug in XFS that was fixed recently, otherwise my stat would still be 0. In most cases, after an unclean shutdown, the journal is replayed and everything is fine. Otherwise you either hit a bug (that needs fixing), or you have hardware problems. -- Matthias |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [PATCH] xfs: fix ASSERTION failure in xfs_vm_write_failed(), Jeff Liu |
|---|---|
| Next by Date: | Экспертиза смет, Контроль сроков выполнения работ |
| Previous by Thread: | Re: Xfs_repair and journalling, Stan Hoeppner |
| Next by Thread: | Re: Xfs_repair and journalling, Dave Chinner |
| Indexes: | [Date] [Thread] [Top] [All Lists] |