Hi,
On Saturday 25 June 2016 23:22:06 Pranay Srivastava wrote:
> On Fri, Jun 24, 2016 at 2:59 PM, Markus Pargmann wrote:
> > From: "Pranay Kr. Srivastava"
> >
> > When a timeout occurs or a recv fails, then instead of abruplty killing
> > nbd block device wait for it's users to finish.
> >
> > T
On Fri, Jun 24, 2016 at 2:59 PM, Markus Pargmann wrote:
> From: "Pranay Kr. Srivastava"
>
> When a timeout occurs or a recv fails, then instead of abruplty killing
> nbd block device wait for it's users to finish.
>
> This is more required when filesystem(s) like ext2 or ext3 don't expect
> their
On 06/24/2016 03:29 AM, Markus Pargmann wrote:
> From: "Pranay Kr. Srivastava"
>
> When a timeout occurs or a recv fails, then instead of abruplty killing
s/abruplty/abruptly/
> nbd block device wait for it's users to finish.
s/it's/its/ (remember, "it's" is only usable where "it is" would als
Hey Markus,
On Fri, Jun 24, 2016 at 2:59 PM, Markus Pargmann wrote:
> From: "Pranay Kr. Srivastava"
>
> When a timeout occurs or a recv fails, then instead of abruplty killing
> nbd block device wait for it's users to finish.
>
> This is more required when filesystem(s) like ext2 or ext3 don't e
From: "Pranay Kr. Srivastava"
When a timeout occurs or a recv fails, then instead of abruplty killing
nbd block device wait for it's users to finish.
This is more required when filesystem(s) like ext2 or ext3 don't expect
their buffer heads to disappear while the filesystem is mounted.
Each ope
5 matches
Mail list logo