View previous topic :: View next topic |
Author |
Message |
nsh n00b
Joined: 25 Nov 2012 Posts: 5
|
Posted: Mon Nov 26, 2012 11:08 pm Post subject: fsck finds jfs corrupted(?) on every reboot (mdadm/RAID1) |
|
|
Hi,
I have software RAID1 (using mdadm) on all my partitions (all jfs).
mdadm fails to unmount my / and /usr partitions like in this post: https://forums.gentoo.org/viewtopic-t-923332-highlight-mdraid+stop.html
Despite everyone says "it's OK", it looks to me that that something is going wrong in my specific case as on each reboot fsck finds jfs corrupted (if I am not mistaken - see the below log) and has to replay the journal logs:
Code: | 11/26/12 05:53:11 PM * Checking local filesystems ...
11/26/12 05:53:11 PM fsck.jfs version 1.1.15, 04-Mar-2011
11/26/12 05:53:11 PM processing started: 11/26/2012 17:38:03
11/26/12 05:53:11 PM The current device is: /dev/md126
11/26/12 05:53:11 PM Block size in bytes: 4096
11/26/12 05:53:11 PM Filesystem size in blocks: 2441198
11/26/12 05:53:11 PM **Phase 0 - Replay Journal Log
11/26/12 05:53:11 PM Filesystem is clean.
11/26/12 05:53:11 PM fsck.jfs version 1.1.15, 04-Mar-2011
11/26/12 05:53:11 PM processing started: 11/26/2012 17:38:04
11/26/12 05:53:11 PM The current device is: /dev/md121
11/26/12 05:53:11 PM Block size in bytes: 4096
11/26/12 05:53:11 PM Filesystem size in blocks: 243965
11/26/12 05:53:11 PM **Phase 0 - Replay Journal Log
11/26/12 05:53:11 PM Filesystem is clean.
11/26/12 05:53:11 PM fsck.jfs version 1.1.15, 04-Mar-2011
11/26/12 05:53:11 PM processing started: 11/26/2012 17:38:04
11/26/12 05:53:11 PM The current device is: /dev/md123
11/26/12 05:53:11 PM Block size in bytes: 4096
11/26/12 05:53:11 PM Filesystem size in blocks: 24413678
11/26/12 05:53:11 PM **Phase 0 - Replay Journal Log
11/26/12 05:53:11 PM Filesystem is clean.
11/26/12 05:53:11 PM fsck.jfs version 1.1.15, 04-Mar-2011
11/26/12 05:53:11 PM processing started: 11/26/2012 17:38:04
11/26/12 05:53:11 PM The current device is: /dev/md124
11/26/12 05:53:11 PM Block size in bytes: 4096
11/26/12 05:53:11 PM Filesystem size in blocks: 2441198
11/26/12 05:53:11 PM **Phase 0 - Replay Journal Log
11/26/12 05:53:11 PM Filesystem is clean.
11/26/12 05:53:11 PM fsck.jfs version 1.1.15, 04-Mar-2011
11/26/12 05:53:11 PM processing started: 11/26/2012 17:38:04
11/26/12 05:53:11 PM The current device is: /dev/md125
11/26/12 05:53:11 PM Block size in bytes: 4096
11/26/12 05:53:11 PM Filesystem size in blocks: 12206830
11/26/12 05:53:11 PM **Phase 0 - Replay Journal Log
11/26/12 05:53:11 PM Filesystem is clean.
11/26/12 05:53:11 PM fsck.jfs version 1.1.15, 04-Mar-2011
11/26/12 05:53:11 PM processing started: 11/26/2012 17:38:04
11/26/12 05:53:11 PM The current device is: /dev/md127
11/26/12 05:53:11 PM Block size in bytes: 4096
11/26/12 05:53:11 PM Filesystem size in blocks: 194385551
11/26/12 05:53:11 PM **Phase 0 - Replay Journal Log
11/26/12 05:53:11 PM Filesystem is clean.
|
Does it really look OK? If it is not, any piece of advice on how to fix it, please?
Thanks in advance,
-nsh |
|
Back to top |
|
|
The Doctor Moderator
Joined: 27 Jul 2010 Posts: 2678
|
Posted: Mon Nov 26, 2012 11:47 pm Post subject: |
|
|
I don't see corruption. JFS always replays its log before mounting rw. That is what you have to have the 'ro' kernel parameter, if I remember correctly. _________________ First things first, but not necessarily in that order.
Apologies if I take a while to respond. I'm currently working on the dematerialization circuit for my blue box. |
|
Back to top |
|
|
nsh n00b
Joined: 25 Nov 2012 Posts: 5
|
Posted: Tue Nov 27, 2012 12:49 am Post subject: |
|
|
The Doctor wrote: | I don't see corruption. JFS always replays its log before mounting rw. That is what you have to have the 'ro' kernel parameter, if I remember correctly. |
Thanks, I did not know that.
I have ro in kernel parameters. |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|