Bug #16168
closedjewel: ENAMETOOLONG osd init failure lingering in jewel test -- need to add the config or force it to use xfs
0%
Description
sjust@teuthology:/a/samuelj-2016-06-05_21:24:33-rados-wip-16113-jewel-distro-basic-smithi/239533$
description: rados/thrash/{hobj-sort.yaml rados.yaml 0-size-min-size-overrides/3-size-2-min-size.yaml
1-pg-log-overrides/short_pg_log.yaml clusters/{fixed-2.yaml openstack.yaml} fs/ext4.yaml
msgr/async.yaml msgr-failures/osd-delay.yaml thrashers/morepggrow.yaml workloads/rados_api_tests.yaml}
Updated by Samuel Just almost 8 years ago
- Subject changed from ENAMETOOLONG osd init failure lingering in jewel test -- need to add the config or force it to use xfs to jewel: ENAMETOOLONG osd init failure lingering in jewel test -- need to add the config or force it to use xfs
- Priority changed from Normal to Urgent
Updated by Zezhu Zhang almost 8 years ago
I force it to use xfs:
rados:thrash/{hobj-sort.yaml rados.yaml rocksdb.yaml 0-size-min-size-overrides/3-size-2-min-size.yaml 1-pg-log-overrides/normal_pg_log.yaml clusters/{fixed-2.yaml openstack.yaml} fs/xfs.yaml msgr/simple.yaml msgr-failures/osd-delay.yaml thrashers/morepggrow.yaml workloads/cache-agent-small.yaml}
but also print WARNING: max attr value size (1024) is smaller than osd_max_object_name_len (2048). Your backend filesystem appears to not support attrs large enough to handle the configured max rados name size. You may get unexpected ENAMETOOLONG errors on rados operations or buggy behavior