165 reputation
17
bio website
location
age
visits member for 4 years, 5 months
seen Oct 30 '12 at 11:51

Mar
20
awarded  Notable Question
May
27
awarded  Teacher
Oct
30
comment fsck: FILE SYSTEM WAS MODIFIED after each check with -c, why?
"The bad blocks list is updated any time badblocks (or fsck -c) runs. That's a stupid design decision." That was what I wanted to be confirmed. Thanks.
Oct
30
accepted fsck: FILE SYSTEM WAS MODIFIED after each check with -c, why?
Jul
24
awarded  Commentator
Jul
24
comment fsck: FILE SYSTEM WAS MODIFIED after each check with -c, why?
About your comment: Yes I know, but as I mentioned in my question, I'm talking about CF cards. Unfortunately it is not possible to change hardware as easy as in your personal computer when talking about embedded systems with several thousand installed pieces.
Jul
24
comment fsck: FILE SYSTEM WAS MODIFIED after each check with -c, why?
First of all, thanks for the response. My question a) is answered, it originated in a misunderstanding of what is exactly meant with the file system and yes, I am capable of reading. Still, I cannot see the answer to b). Why is the bad block inode modified if there were no bad blocks? so, you ask, why does it return 1 when you specify -n No.
Jun
28
awarded  Popular Question
Jun
28
comment What exactly does the automated ext3 root file system check?
Thanks again. With question 2) I wanted to ask you how you know these things - is it your own experience, or do you cite a document? Thanks also for the general thoughts and concerns about CF, although this was not part of my question. Unfortunately I cannot influence it...
Jun
27
comment What exactly does the automated ext3 root file system check?
Thanks for your answer. What do you mean with "full fsck"? Where does the information come from? Yes I know the flags, it is not my question how the fsck is triggered, but what it actually does -- can it be configured to repair and not only check?
Jun
15
comment What exactly does the automated ext3 root file system check?
I'm not sure about this, in a narrow sense the problem is not OS specific, it is more about the ext3 file system. But since ext3 is closely related to Linux, it would probably also be correct to ask the question there...
Jun
15
asked What exactly does the automated ext3 root file system check?
Jan
11
awarded  Popular Question
Jul
27
awarded  Tumbleweed
May
17
comment fsck: FILE SYSTEM WAS MODIFIED after each check with -c, why?
This makes no sense to me, running 'fsck -n /dev/sdx1' works fine with return value 0, as well as 'badblocks /dev/sdx1'. But the combination of both, 'fsck -cn /dev/sdx1', alters the file system and ends with return value 1 each time? I'm confused.
May
17
comment fsck: FILE SYSTEM WAS MODIFIED after each check with -c, why?
Thanks for the -v hint, but this does not help a lot. badblocks runs fine with return value 0.
May
17
accepted Refresh devices - reconnect CF card drive by script (unplug-plug equivalent)
May
12
asked fsck: FILE SYSTEM WAS MODIFIED after each check with -c, why?
May
12
answered Refresh devices - reconnect CF card drive by script (unplug-plug equivalent)
May
12
comment Refresh devices - reconnect CF card drive by script (unplug-plug equivalent)
Thanks for the hint, but while 'partprobe -s' detects the partitions correctly, the '/proc/partitions' file and the device nodes are not updated.