On Tue, Sep 11, 2018 at 1:34 AM <[email protected]> wrote: > > From: Ocean He <[email protected]> > > When namespace creation failure occurs, the consumed namespace (seed or 0th > idle) and pfn/dax seed would block next namespace creation. A recovery is > needed to handle this type failure. > > A symptom example (section size is 128MB) based on kernel 4.19-rc2 and > ndctl v62: > # ndctl create-namespace -r region1 -s 100m -t pmem -m fsdax > { > "dev":"namespace1.0", > "mode":"fsdax", > "map":"dev", > "size":"96.00 MiB (100.66 MB)", > "uuid":"ef9a0556-a610-40b5-8c71-43991765a2cc", > "raw_uuid":"177b22e2-b7e8-482f-a063-2b8de876d979", > "sector_size":512, > "blockdev":"pmem1", > "numa_node":1 > } > # ndctl create-namespace -r region1 -s 100m -t pmem -m fsdax > libndctl: ndctl_pfn_enable: pfn1.1: failed to enable > Error: namespace1.1: failed to enable > failed to create namespace: No such device or address > # ndctl destroy-namespace namespace1.0 -f > destroyed 1 namespace > # ndctl create-namespace -r region1 -s 128m -t pmem -m fsdax > failed to create namespace: Device or resource busy > > Signed-off-by: Ocean He <[email protected]>
Apologies, this got lost in my inbox. Looks good, and tests ok as well. Reviewed-by: Dan Williams <[email protected]> _______________________________________________ Linux-nvdimm mailing list [email protected] https://lists.01.org/mailman/listinfo/linux-nvdimm
