[Bug 200753] write I/O error for inode structure leads to operation failure without any warning or error

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



https://bugzilla.kernel.org/show_bug.cgi?id=200753

Theodore Tso (tytso@xxxxxxx) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tytso@xxxxxxx

--- Comment #7 from Theodore Tso (tytso@xxxxxxx) ---
Shehbaz,

Before you file more bugs, perhaps you should describe what your model is for
how a file system should behave.  You seem to have some very confused ideas for
how a file system should behave in the face of I/O errors (e.g., thinking that
a symlink to an inode which is in a broken inode table block MUST be a file
system error).

Why don't you write up a document that describes how you think the world works,
because it seems like a waste of your time to create these very careful bug
reports with reproductions when you seem to be operated on a fundamental flawed
model of how a file system behaves, and how it should behave in the face of
errors.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.



[Index of Archives]     [Reiser Filesystem Development]     [Ceph FS]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Linux FS]     [Yosemite National Park]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Device Mapper]     [Linux Media]

  Powered by Linux