LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Debian (https://www.linuxquestions.org/questions/debian-26/)
-   -   flag is clear, journal has data (https://www.linuxquestions.org/questions/debian-26/flag-is-clear-journal-has-data-721167/)

j1alu 04-23-2009 09:47 AM

flag is clear, journal has data
 
i did a bit of searching and that error-message during boot seems to be common
during the boot-filesystem-check:
Quote:

"/dev/sdaXX Supberblock needs-recovery flag is clear, but journal has data
run jounal anyway :
yes
UNEXPECTED INCONSITENCY, RUN fsck manuallly"
after installing kde4-minimal on sid.


i ran the e2fsck on /dev/sdaX, the following boot went fine,
next boot: same problem, different partition.

after it has happened four times i purged kde4 and all is fine again.
whats the problem?the upgrade of xsever-xorg?or is kde4 broken in sid?
(i dunno what a superblock is, what a flag is and what a journal is, for me its all darkness :-))
if one might explain in easy words or give me a link?, i just wanna understand what has happened, i got no big interest in installing kde4 now ( the gui-fights i have to fight are in the light now:-))

greetings

farslayer 04-24-2009 07:49 AM

I wouldn't call it common. I've seen it maybe once or twice in the past 5 years, due to powerloss or a hard system shutdown. ..

It sounds like something isn't finished writing data to the hard drive before the system shuts down. the system is failing to sync before it's powered off.

Superblockl, flag and journal in this instance are all part of your file system.

Since this only occurs when you are running KDE then I would guess that is where the issue lies, the question is why and how do you fix it ?

For testing you could install KDE4 Configure it so it does NOT start automatically at boot.
Boot the system, log in, manually Start X and use it.
When you are done working shut down X, manually sync the filesystem using the sync command linked above. then shutdown.
I would bet using that process, the corruption will not show up again.
The problem is, that should all happen automatically, in the background, without you being aware of the process

j1alu 04-24-2009 11:27 AM

thanks,
its more clear now to me, as i had big trouble with both:logging out and shutting down the system. i`m not sure if i have tried it with and without kdm or only with kdm, but for sure i didn`t just hit the power-off button (as it would have been a hint).

I`ll have a look at the link and maybe try what you`ve adviced/proposed these days, else i`ll just study sync. [first i have to understand whats going on with xserver-xorg after the last upgrade (~1.7?)]
thanks again -big help:)- and greetings

mmh: i`ve read the manual of sync: i would just run >sync> from the login-shell
and after that <shutdown -r now<.


All times are GMT -5. The time now is 04:53 AM.