On Jan 13, 2014, at 8:34, Trond Myklebust
wrote:
>
> On Jan 13, 2014, at 2:55, shaobingqing wrote:
>
>> When a file is in NFS_INO_LAYOUTCOMMITING status, its isize perhaps has not
>> been
>> transferred to the metadate server. So the isize getting from the metadata
>> server
>> perhaps
On Jan 13, 2014, at 2:55, shaobingqing wrote:
> When a file is in NFS_INO_LAYOUTCOMMITING status, its isize perhaps has not
> been
> transferred to the metadate server. So the isize getting from the metadata
> server
> perhaps is out of date and cannot be used to update the isize of the
When a file is in NFS_INO_LAYOUTCOMMITING status, its isize perhaps has not
been
transferred to the metadate server. So the isize getting from the metadata
server
perhaps is out of date and cannot be used to update the isize of the client.
Signed-off-by: shaobingqing
---
fs/nfs/inode.c |
When a file is in NFS_INO_LAYOUTCOMMITING status, its isize perhaps has not
been
transferred to the metadate server. So the isize getting from the metadata
server
perhaps is out of date and cannot be used to update the isize of the client.
Signed-off-by: shaobingqing shaobingq...@bwstor.com.cn
On Jan 13, 2014, at 2:55, shaobingqing shaobingq...@bwstor.com.cn wrote:
When a file is in NFS_INO_LAYOUTCOMMITING status, its isize perhaps has not
been
transferred to the metadate server. So the isize getting from the metadata
server
perhaps is out of date and cannot be used to update
On Jan 13, 2014, at 8:34, Trond Myklebust trond.mykleb...@primarydata.com
wrote:
On Jan 13, 2014, at 2:55, shaobingqing shaobingq...@bwstor.com.cn wrote:
When a file is in NFS_INO_LAYOUTCOMMITING status, its isize perhaps has not
been
transferred to the metadate server. So the isize
6 matches
Mail list logo
