| To: | markgw@xxxxxxx |
|---|---|
| Subject: | Re: RFC: log record CRC validation |
| From: | Michael Nishimoto <miken@xxxxxxxxx> |
| Date: | Thu, 26 Jul 2007 10:53:02 -0700 |
| Cc: | David Chinner <dgc@xxxxxxx>, xfs-dev <xfs-dev@xxxxxxx>, xfs-oss <xfs@xxxxxxxxxxx> |
| In-reply-to: | <46A7226D.8080906@xxxxxxx> |
| References: | <20070725092445.GT12413810@xxxxxxx> <46A7226D.8080906@xxxxxxx> |
| Sender: | xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax) |
Mark Goodwin wrote: David Chinner wrote: > > The next question is the hard one. What do we do when we detect > a log record CRC error? Right now it just warns and sets a flag > in the log. I think it should probably prevent log replay from > replaying past this point (i.e. trim the head back to the last > good log record) but I'm not sure what the best thing to do here. > > Comments?1. perhaps use a new flag XLOG_CRC_MISMATCH instead of XLOG_CHKSUM_MISMATCH 2. is there (or could there be if we added it), correction for n-bit errors?-- Mark I don't see the original message in the archives. Is CRC checking being added to xfs log data? If so, what data has been collected to show that this needs to be added? thanks, Michael |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: RFC: log record CRC validation, David Chinner |
|---|---|
| Next by Date: | Re: xfsqa 144 is failing now, Christoph Hellwig |
| Previous by Thread: | Re: RFC: log record CRC validation, David Chinner |
| Next by Thread: | Re: RFC: log record CRC validation, David Chinner |
| Indexes: | [Date] [Thread] [Top] [All Lists] |