sorry, forgot to add: i’m using 4k drives with tests. but i have no found message about : it can’t be used with zfs tests? or we can use 4k drives? what about 'newfs' with ufs - is it support 4k drives? or - we have to work on aonther scenarios for 4K ?
-Igor > On Jun 22, 2018, at 1:40 AM, Igor Kozhukhov <[email protected]> wrote: > > Hi All, > > i try to invstigate issues with ZFS test on my env and i have found issue > with zfs_destroy_005_neg > > full log only with this test: > > https://paste.dilos.org/?fef1dc1ce4b9e3c7#BYJ192rOQZzuoyfQCvoi/BElI/5ZEpdJiI0jzn1DcJY= > > <https://paste.dilos.org/?fef1dc1ce4b9e3c7#BYJ192rOQZzuoyfQCvoi/BElI/5ZEpdJiI0jzn1DcJY=> > > it failed at end with : > rm: cannot remove '/testdir1': Device busy > 01:28:20.32 ERROR: rm -rf /testdir1 exited 1 > > because - we have to do : umount /testdir1 > before 'rm' it. > > I’m interested in test on another env to be sure - probably it related to my > env or not. > > after this test 'cleanup' will be failed, several tests will be SKIPed > because setup failed and far far later i can see panic - but very hard > identify start point what can be related to panic, because a lot of tests > failed with unknown reason. > > I think, we have some inconsisnetcy with tests logic. > I think, will be much more better - to stop next tests if 'clean' procedure > faied - because it can do impacts to 'setup' for next tests and impacts to > others tests. > with stop tests will be much more easy identify step - where we are failed > first - and have to investigate it before next tests. > > best regards, > -Igor > ------------------------------------------ openzfs: openzfs-developer Permalink: https://openzfs.topicbox.com/groups/developer/Tc92538cb23c4b71b-Md43560773d5dd45aede94ce5 Delivery options: https://openzfs.topicbox.com/groups
