Re: 7-STABLE, gjournal and fsck.

David N wrote:
2008/8/3 Eugene Butusov <ebutusov@xxxxxxxxx>:
Hi,

Recently I've decided to play with gjournal. Main reason was a promise of
avoiding full fsck check after unclean shutdown. I've successfuly configured
gjournal on existing filesystems (all UFS). And then it happened - my system
had a power failure. After boot, it forced me to run fsck manualy. Nothing
special, I did it before... But this time it failed on gjournaled disks.

So, when I was dropped to the single-user shell, I tried:

fsck /dev/ad4s1g.journal

It said:

CANNOT READ BLK: xxxx
CONTINUE? [yn]

I typed 'y' and nothing happened. Here is the log:

-8<-
Aug 2 19:13:43 matrix kernel: GEOM_JOURNAL: Journal 4059706613: ad4s1g
contains data.
Aug 2 19:13:43 matrix kernel: GEOM_JOURNAL: Journal 4059706613: ad4s1g
contains journal.
Aug 2 19:13:43 matrix kernel: GEOM_JOURNAL: Journal ad4s1g clean.
Aug 2 19:13:43 matrix kernel: GEOM_JOURNAL: Journal 188084099: ad6s1d
contains data.
Aug 2 19:13:43 matrix kernel: GEOM_JOURNAL: Journal 188084099: ad6s1d
contains journal.
Aug 2 19:13:43 matrix kernel: GEOM_JOURNAL: Journal ad6s1d clean.
Aug 2 19:13:43 matrix kernel: GEOM_JOURNAL: Journal 2559963968: ad6s1e
contains data.
Aug 2 19:13:43 matrix kernel: GEOM_JOURNAL: Journal 2559963968: ad6s1e
contains journal.
Aug 2 19:13:43 matrix kernel: GEOM_JOURNAL: Journal ad6s1e clean.
...
Aug 2 19:13:43 matrix kernel: ** /dev/ad4s1g.journal
Aug 2 19:13:43 matrix kernel:
Aug 2 19:13:43 matrix kernel: CANNOT READ BLK: 727112224
Aug 2 19:13:43 matrix kernel: CONTINUE? [yn]
Aug 2 19:13:43 matrix kernel:
Aug 2 19:13:43 matrix kernel: THE FOLLOWING DISK SECTORS COULD NOT BE READ:
727112224, 727112225, 727112226, 727112227,
Aug 2 19:13:43 matrix kernel: /dev/ad4s1g.journal: CANNOT FIGURE OUT FILE
SYSTEM PARTITION
->8-

After ctrl+d the system tried to continue boot, and again threw me into
shell because of the same reason:

-8<-
Aug 2 19:13:43 matrix kernel:
WARNING: R/W mount of /home denied. Filesystem is not clean - run fsck
Aug 2 19:13:43 matrix kernel: mount:
->8-

Like I mentioned, only gjournaled filesystems failed to pass fsck. Other
labels passed. I was in a hurry, because the machine acts as a local file
server, and I was standing against the wall, because one of gjournaled disks
was the share itself...

What I did was mounting gjournaled partitions in ro mode (it warned me that
they were not cleanly unmounted) and doing some backup. Then I removed
gjournal (gjournal clear, tunefs -J disable) from journaled disks, ran fsck
(few errors of type: PARTIALLY ALLOCATED INODE), and then I was able to turn
on softupdates back and mount the fs in rw mode. I've double checked the
disk's SMART results in case of hardware failure, but they were ok.

My question is: what could cause such problem? Why only gjournaled fs are
affected? Is there a solution?

Best regards,
--
_/_/ .. Eugene Butusov
_/_/ ... www.devilka.info
_/_/ .... ebutusov(at)gmail(dot)com
_______________________________________________
freebsd-stable@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe@xxxxxxxxxxx"


Hi,

Did you re-create your file systems? How did you create the journal?

eg. newfs /dev/ad4s1g.journal ?

or did you just enable journal on the partition? via tunefs?

I did it this way:

/dev/ad4s1g is my /home, an existing partition

umount /home
gjournal label -f /dev/ad4s1g
tunefs -J enable -n disable /dev/ad4s1g.journal
(added 'async' option to /etc/fstab for /home and changed entry to /dev/ad4s1g.journal)
mount /home

It worked until power failed... :)

Best regards,
--
_/_/ .. Eugene Butusov
_/_/ ... www.devilka.info
_/_/ .... ebutusov(at)gmail(dot)com
_______________________________________________
freebsd-stable@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe@xxxxxxxxxxx"

Relevant Pages

  • Re: [SLE] fsck!!!
    ... >> that is needed during the manual fsck part. ... >> You need to boot the rescue system, from the CD or DVD, not from the HD. ... > ACPI disabled, Install - Safe settings, Manual install, Rescue System, ... You need to have somethings printed before hand: the partition table, ...
    (SuSE)
  • Re: [SLE] Booting Problem
    ... Please repair manually and reboot. ... except rebooting during the installation. ... > 'fsck failed' again. ... that normally it is NOT a problem with a partition gone bad. ...
    (SuSE)
  • Re: [SLE] fsck!!!
    ... If the problem is in the root partition, ... Also, considering your fstab: ... > that is needed during the manual fsck part. ... >>local harddisk, boot safely, rescue mode and a couple of others. ...
    (SuSE)
  • Re: How do I run an ??????????????????
    ... with "fsck" replaced appropriately. ... Mac OS X at all, certainly not in single user mode. ... Boot from your Mac OS X partition, ... While I am glad to learn of this previously unknown way to use DiskWarrior, in the present case it brought about the same result as before: DiskWarrior started rebuilding directories but was slowed by malfunctions. ...
    (comp.sys.mac.apps)
  • disk recovery help
    ... fsck was able to fix / with no problems, ... vpopmail/qmail/courier-imap-pop) in case there was any corrupted gunk left ... However the partition holding all the mail (in Maildir ... and then try to fsck without any time pressure and see what ...
    (freebsd-hackers)