From: Theodore Ts'o <tytso@mit.edu>
To: "Lukáš Czerner" <lczerner@redhat.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: [PATCH v2] ext4: add sysfs entry showing whether the fs contains errors
Date: Wed, 7 May 2014 12:01:52 -0400 [thread overview]
Message-ID: <20140507160152.GA6408@thunk.org> (raw)
In-Reply-To: <alpine.LFD.2.00.1405071714470.2128@localhost.localdomain>
On Wed, May 07, 2014 at 05:35:54PM +0200, Lukáš Czerner wrote:
>
> I tried to find sysfs guidelines but I can not see any in
> Documentation speaking about the contents of the files.
>
> What are the guidelines then ?
Documentation/filesystems/sysfs.txt:
Attributes can be exported for kobjects in the form of regular
files in the filesystem. Sysfs forwards file I/O operations to
methods defined for the attributes, providing a means to read and
write kernel attributes.
Attributes should be ASCII text files, preferably with only one value
per file. It is noted that it may not be efficient to contain only one
value per file, so it is socially acceptable to express an array of
values of the same type.
I don't remember that last sentence; it was apparently added since the
last time I've looked at it. Originally, the requirement that each
sysfs file (which was supposed to be an kobject attribute) was
required to be a single value. Now there's an escape hatch for
"efficiency", which is nice....
> So you're suggesting to have three sysfs files ?
>
> errors_count
> first_error_time
> last_error_time
Yes, that's what I was suggesting.
- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-05-07 16:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-07 12:04 [PATCH v2] ext4: add sysfs entry showing whether the fs contains errors Lukas Czerner
2014-05-07 14:36 ` Theodore Ts'o
2014-05-07 15:35 ` Lukáš Czerner
2014-05-07 16:01 ` Theodore Ts'o [this message]
2014-05-07 16:03 ` Lukáš Czerner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140507160152.GA6408@thunk.org \
--to=tytso@mit.edu \
--cc=lczerner@redhat.com \
--cc=linux-ext4@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).