On Mon, Feb 05, 2018 at 02:45:21PM +0800, Anand Jain wrote:
> On 02/05/2018 02:38 PM, Anand Jain wrote:
> > On 02/03/2018 03:09 AM, Howard McLauchlan wrote:
> >> Presently, failing a primary super block write but succeeding in at
> >> least one super block write in general will appear to users as i
On Fri, Feb 02, 2018 at 11:19:59AM -0800, Howard McLauchlan wrote:
> On 02/02/2018 11:09 AM, Howard McLauchlan wrote:
> > Presently, failing a primary super block write but succeeding in at
> > least one super block write in general will appear to users as if
> > nothing important went wrong. Howev
On 02/05/2018 02:38 PM, Anand Jain wrote:
On 02/03/2018 03:09 AM, Howard McLauchlan wrote:
Presently, failing a primary super block write but succeeding in at
least one super block write in general will appear to users as if
nothing important went wrong.
However, upon unmounting and re-mo
On 02/03/2018 03:09 AM, Howard McLauchlan wrote:
Presently, failing a primary super block write but succeeding in at
least one super block write in general will appear to users as if
nothing important went wrong.
However, upon unmounting and re-mounting,
the file system will be in a rolled b
On 02/02/2018 11:09 AM, Howard McLauchlan wrote:
> Presently, failing a primary super block write but succeeding in at
> least one super block write in general will appear to users as if
> nothing important went wrong. However, upon unmounting and re-mounting,
> the file system will be in a rolled
Presently, failing a primary super block write but succeeding in at
least one super block write in general will appear to users as if
nothing important went wrong. However, upon unmounting and re-mounting,
the file system will be in a rolled back state. This was discovered
with a BCC program that u
