From: Martin Steigerwald <Martin@lichtvoll.de>
To: xfs@oss.sgi.com
Subject: Re: Xfs_repair and journalling
Date: Mon, 18 Mar 2013 21:50:34 +0100 [thread overview]
Message-ID: <201303182150.34665.Martin@lichtvoll.de> (raw)
In-Reply-To: <CAEUQceie41dh7h6uZSMu4-JB_BDu82X5CrKxHb=9wVQVAPzKgQ@mail.gmail.com>
Am Sonntag, 17. März 2013 schrieb Subranshu Patel:
> 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.
USB stick with Ext4 without any mkfs options:
merkaba:~> mount /dev/sdb /mnt/zeit
merkaba:~> rsync -a /etc /mnt/zeit
(was to short)
merkaba:~> rsync -a /usr/bin /mnt/zeit
Unplug during write activity:
merkaba:~> grep "journal" /var/log/syslog | tail -5
Mar 18 21:43:22 merkaba kernel: [29938.038298] journal commit I/O error
Mar 18 21:43:22 merkaba kernel: [29938.038300] journal commit I/O error
Mar 18 21:43:22 merkaba kernel: [29938.038302] journal commit I/O error
Mar 18 21:43:22 merkaba kernel: [29938.038305] journal commit I/O error
Mar 18 21:43:22 merkaba kernel: [29938.038308] journal commit I/O error
merkaba:~> grep -c "journal commit" /var/log/syslog
1915
Wait till KDE SC stops replaying these notifications and then restart
plasma-desktop to get rid of it cause that takes to long.
Plug USB stick back in. And mount it:
merkaba:~> mount /dev/sdc /mnt/zeit
merkaba:~> ls -l /mnt/zeit
insgesamt 40
drwxr-xr-x 2 root root 12288 Mär 18 21:43 bin
drwxr-xr-x 188 root root 12288 Mär 18 13:31 etc
drwx------ 2 root root 16384 Mär 18 21:42 lost+found
Mount took about 5 seconds.
merkaba:~> dmesg | tail -2
[30217.601896] EXT4-fs (sdc): recovery complete
[30217.603287] EXT4-fs (sdc): mounted filesystem with ordered data mode.
Opts: (null)
So can we get over any guess work that Ext4 might not be able to replay
its journal after an unclean shutdown?
It can and it does. And not just since this 3.9-rc3 kernel.
Thanks,
--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-03-18 20:50 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-16 15:56 Xfs_repair and journalling Subranshu Patel
2013-03-17 2:22 ` Stan Hoeppner
2013-03-17 3:01 ` Michael L. Semon
2013-03-17 5:26 ` Stan Hoeppner
2013-03-17 11:42 ` Subranshu Patel
2013-03-17 14:50 ` Stan Hoeppner
2013-03-17 15:18 ` Matthias Schniedermeyer
2013-03-17 23:20 ` Dave Chinner
2013-03-18 18:22 ` Ben Myers
2013-03-18 20:58 ` Martin Steigerwald
2013-03-18 20:50 ` Martin Steigerwald [this message]
2013-03-19 4:02 ` Eric Sandeen
2013-03-19 6:19 ` Stan Hoeppner
2013-03-19 8:24 ` Martin Steigerwald
2013-03-19 10:14 ` Stan Hoeppner
2013-03-30 12:49 ` Xfs_repair and journalling -- EXT4 journal replay discussion Stan Hoeppner
2013-03-30 17:40 ` Eric Sandeen
2013-03-30 18:52 ` Stan Hoeppner
2013-03-30 20:21 ` Eric Sandeen
2013-03-31 11:24 ` Stan Hoeppner
2013-03-31 2:03 ` Dave Chinner
2013-03-31 1:35 ` Dave Chinner
2013-03-18 20:37 ` Xfs_repair and journalling Martin Steigerwald
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201303182150.34665.Martin@lichtvoll.de \
--to=martin@lichtvoll.de \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox