On 6/28/15 5:29 PM, Timofey Titovets wrote: > 2015-06-29 1:12 GMT+03:00 Eric Sandeen <sandeen@xxxxxxxxxxx>: ... >> You're likely just seeing that inconsitency because you're reading >> it while it's mounted; possibly even while it's being modified. >> >> -Eric > > I already thinked about this case, and it seems incredible. > 1. i can get consistent or very close to consistent fs, by run 'sync' > 2. Okay, supposing you are right, > then i must get different errors over time, because fs will change own > state over time (also after every sync call). > But its don't happen, i get same errors over long period of time (1 > day+, i think on busy FS server, its enoug to think what data on disk > has changed) > Also, i have several others server, and on it i didn't see this > problem (over 2-3 month). > > > Then I can conclude this is errors in FS, only what matter to me now, > this type of errors can damage my data and i must move virtual > machines from it ASAP, or i can continue working and this is just > "artefact". > > Fix me if i'm wrong. Your other option is to unmount and run xfs_repair, and find out if you actually have on-disk corruption. It's the only way to know for sure (or: freeze the fs, snapshot the device, and run repair on that) -Eric -Eric _______________________________________________ xfs mailing list xfs@xxxxxxxxxxx http://oss.sgi.com/mailman/listinfo/xfs
