From 2dc5cf8e1c0890b4d453fcb104c7818cba77c4fb Mon Sep 17 00:00:00 2001 From: Andreas Dilger Date: Fri, 10 May 2013 14:22:10 -0600 Subject: [PATCH] LU-3187 obdecho: always set o_id non-zero Always initialize the o_id field in obdecho requests so the server doesn't get confused between o_id == 0 and f_seq == 0. This isn't strictly necessary for protocol correctness (the server assigns the actual OID in the end), but makes life a bit easier for cross compatibility with FID-on-OST. Signed-off-by: Andreas Dilger Change-Id: Ifc318333df97326fb33366cd9f06d33e3f5139bb Reviewed-on: http://review.whamcloud.com/6319 Tested-by: Hudson Tested-by: Maloo Reviewed-by: Lai Siyao Reviewed-by: Oleg Drokin --- lustre/utils/obd.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lustre/utils/obd.c b/lustre/utils/obd.c index 5946c5c..b2f12da 100644 --- a/lustre/utils/obd.c +++ b/lustre/utils/obd.c @@ -1051,7 +1051,7 @@ int jt_obd_create(int argc, char **argv) char rawbuf[MAX_IOC_BUFLEN], *buf = rawbuf; struct obd_ioctl_data data; struct timeval next_time; - __u64 count = 1, next_count, base_id = 0; + __u64 count = 1, next_count, base_id = 1; int verbose = 1, mode = 0100644, rc = 0, i, valid_lsm = 0; char *end; -- 1.8.3.1