On Tue, 03/24 11:34, Paolo Bonzini wrote:
>
>
> On 24/03/2015 11:16, Fam Zheng wrote:
> > If issued right after link down, "blockdev --rereadpt" will be stuck for a
> > while and then return normally. Although the underlying capacity and
> > partition
> > table are not correctly updated. And it
On Tue, 03/24 11:34, Paolo Bonzini wrote:
On 24/03/2015 11:16, Fam Zheng wrote:
If issued right after link down, blockdev --rereadpt will be stuck for a
while and then return normally. Although the underlying capacity and
partition
table are not correctly updated. And it means that
On Tue, 03/24 11:34, Paolo Bonzini wrote:
>
>
> On 24/03/2015 11:16, Fam Zheng wrote:
> > If issued right after link down, "blockdev --rereadpt" will be stuck for a
> > while and then return normally. Although the underlying capacity and
> > partition
> > table are not correctly updated. And it
On 24/03/2015 11:16, Fam Zheng wrote:
> If issued right after link down, "blockdev --rereadpt" will be stuck for a
> while and then return normally. Although the underlying capacity and partition
> table are not correctly updated. And it means that userspace can't detect the
> error at all.
>
>
If issued right after link down, "blockdev --rereadpt" will be stuck for a
while and then return normally. Although the underlying capacity and partition
table are not correctly updated. And it means that userspace can't detect the
error at all.
Fix this by propargating the error of "read
On 24/03/2015 11:16, Fam Zheng wrote:
If issued right after link down, blockdev --rereadpt will be stuck for a
while and then return normally. Although the underlying capacity and partition
table are not correctly updated. And it means that userspace can't detect the
error at all.
Fix
On Tue, 03/24 11:34, Paolo Bonzini wrote:
On 24/03/2015 11:16, Fam Zheng wrote:
If issued right after link down, blockdev --rereadpt will be stuck for a
while and then return normally. Although the underlying capacity and
partition
table are not correctly updated. And it means that
If issued right after link down, blockdev --rereadpt will be stuck for a
while and then return normally. Although the underlying capacity and partition
table are not correctly updated. And it means that userspace can't detect the
error at all.
Fix this by propargating the error of read capacity
8 matches
Mail list logo
