[prev in list] [next in list] [prev in thread] [next in thread] 

List:       xindice-dev
Subject:    DO NOT REPLY [Bug 22775]  - Xindice hangs forever on blocking I/O call
From:       bugzilla () apache ! org
Date:       2007-04-28 0:58:33
Message-ID: 20070428005833.945AE714072 () brutus ! apache ! org
[Download RAW message or body]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=22775>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=22775





------- Additional Comments From vgritsenko@apache.org  2007-04-27 17:58 -------
(In reply to comment #5)
> Not necessarily, if 
> 1) File got corrupted after it has been opened

I don't see how it's possible - the file can only grow, IIUC.


> 2) File length and amount of pages are correct, but some pointer to the page got
>  garbage in it and points to non-existing page.

Ok that is scary if it is happening.


> But I agree, it does sound a little paranoid. I'm not sure if it makes sense to
> check it at runtime, introduce a tool to check file integrity, or just fix a bug
> that caused corruption in the first place :)

I would first go with simple one time check on run time (Filer.open() seems to
be a good spot), and a tool for integrity check. See also [1] which is related,
or start a new thread altogether.

http://marc.info/?t=114780880000002&r=1

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
[prev in list] [next in list] [prev in thread] [next in thread]