> That's normally the case, yes, but not here.
Are you saying that if using journal, inconsistencies
in 'clean' fs are expected?
Basically I'm saying that apparently here journal
does nothing after enabling it.
Usually after really hard power dip, I need
to manually fsck as all symptoms of uncl
2012/8/30 Jakub Lach :
> Yes, if I would answer 'yes' to using journal, there would be unexpected
> free inodes (?) or something like that in syslog and inconsistencies if full
> fsck
> would be performed.
>
That's normally the case, yes, but not here.
> Basically if I have answered 'yes' to using
Yes, if I would answer 'yes' to using journal, there would be unexpected
free inodes (?) or something like that in syslog and inconsistencies if full
fsck
would be performed.
Basically if I have answered 'yes' to using journal, fs would always be
marked
'clean' regardless of state.
--
View th
On Thu, 30 Aug 2012, Jakub Lach wrote:
If I were you, I would try regular fsck, as here
(9-STABLE) using journal has left me with fs
inconsistencies.
Could you elaborate on the inconsistencies you encountered ?
MfG CoCo
___
freebsd-current@freebsd.
2012/8/30 Jakub Lach :
> If I were you, I would try regular fsck, as here
> (9-STABLE) using journal has left me with fs
> inconsistencies.
>
I could do that, but I wonder why fsck_ufs is not able to figure that
out by itself.
René
___
freebsd-current@fr
If I were you, I would try regular fsck, as here
(9-STABLE) using journal has left me with fs
inconsistencies.
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/UFS-journal-error-on-10-0-CURRENT-tp5739231p5739274.html
Sent from the freebsd-current mailing list archive at
Hi,
after a power dip (don't ask how!) my 10.0-amd64 laptop running
r239793 decided to check its file systems.
On /usr it fixed some errors but I am stuck with:
# fsck -y /usr
** /dev/ada0s1f
USE JOURNAL? yes
** SU+J Recovering /dev/ada0s1f
** Reading 33554432 byte journal from inode 5
RECOVER? y
