• Theodore Ts'o's avatar
    e2fsck: correctly propagate error from journal to superblock · fada3660
    Theodore Ts'o authored
    
    If the file system is mounted read-only after a file system error has
    been detected, the fact that an error occurred is written to the
    journal.  This is important because while the journal is getting
    replayed, the error indication in the superblock may very well get
    overwritten.
    
    Unfortunately, the code to propagate the error indication from the
    journal to superblock was broken because this was being done before
    the old file system handle is thrown away and the file system is
    re-opened to ensure that no stale data is in the file system handle.
    As a result, the error indication in the superblock was never written
    out.
    
    To fix this, we need to move the check if the journal's error
    indicator has been set after the file system has been freed and
    re-open.
    Reported-by: default avatarKen Sumrall <ksumrall@google.com>
    Signed-off-by: default avatar"Theodore Ts'o" <tytso@mit.edu>
    fada3660
journal.c 28.6 KB