summaryrefslogtreecommitdiffstats
path: root/fs/jfs/jfs_lock.h
diff options
context:
space:
mode:
authorLukas Czerner <lczerner@redhat.com>2014-09-11 11:18:13 -0400
committerTheodore Ts'o <tytso@mit.edu>2014-09-11 11:18:13 -0400
commit52c198c6820f68b6fbe1d83f76e34a82bf736024 (patch)
tree3c0f9a6c183bf021a765ee36ae5003033a9908cc /fs/jfs/jfs_lock.h
parenta2d4a646e619541e803fb52636964df39aed94b7 (diff)
downloadop-kernel-dev-52c198c6820f68b6fbe1d83f76e34a82bf736024.zip
op-kernel-dev-52c198c6820f68b6fbe1d83f76e34a82bf736024.tar.gz
ext4: add sysfs entry showing whether the fs contains errors
Currently there is no easy way to tell that the mounted file system contains errors other than checking for log messages, or reading the information directly from superblock. This patch adds new sysfs entries: errors_count (number of fs errors we encounter) first_error_time (unix timestamp for the first error we see) last_error_time (unix timestamp for the last error we see) If the file system is not marked as containing errors then any of the file will return 0. Otherwise it will contain valid information. More details about the errors should as always be found in the logs. Signed-off-by: Lukas Czerner <lczerner@redhat.com> Signed-off-by: Theodore Ts'o <tytso@mit.edu>
Diffstat (limited to 'fs/jfs/jfs_lock.h')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud