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: <CAEUQcehjR7cgmYdTZ5_Yv8VuVAdPsL8i1ido9agmu5CzfknJNg@mail.gmail.com>
Date:	Sun, 17 Mar 2013 17:37:14 +0530
From:	Subranshu Patel <spatel.ml@...il.com>
To:	linux-ext4@...r.kernel.org
Subject: Recovery and Journalling

This question is related to recovery (fsck and xfs_repair) and journalling.

I powered off (improper shut down) the system when the IO was
undergoing on mounted EXT4 filesystem.

After that I powered on my machine and then used fsck on the unmounted
filesystem. fsck recovered it.

There are 2 things which I want to confirm:
1. Firstly fsck replays the journal for any unfinished inconsistent writes.
2. Secondly it checks/repairs the other filesystem corruption.

Correct my understanding if wrong.

Consider the above scenario for XFS as well. In XFS, i need to mount
the filesystem, and this automatically replays the journal. After this
I again unmount the filesystem and run xfs_repair.

But in EXT4, i have to run fsck mandatorily before mounting my
filesystem. Please confirm my understanding.
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ