Revision history [back]

oic, replica count on your rings is 1 - that's interesting, I've heard of folks trying to get by with only 2...

the architectural overview gives a brief description of how the names of the files uploaded map to the placement of the data in the cluster: http://docs.openstack.org/developer/swift/overview_architecture.html#the-ring

the replication overview gives a little background on the reason for the file system layout: http://docs.openstack.org/developer/swift/overview_replication.html

The databases are just sqlite, you can take a copy it and open it up and poke at it, the schema's not bad

sqlite3 -line 9d00c9d091fea9ea855f29c22714dc83.db "select * from account_stat"

But the objects themselves will be in .data files similar to the swauth object you inspected with swift-object-info

If you know the names of all the objects and containers you can use:

swift-get-nodes /etc/swift/object.ring.gz AUTH_mainaccount/mycontainer/myobject

If you don't it might be useful first to find the account database for mainaccount - is it in

/srv/1/node/sdb1/accounts/134708/d6c/838d1ece4c89e07201dc996b91d10d6c/

Is everything on 10.180.32.20?

How many account databases could there be really?

find /srv/node1/sdb1/accounts/ -name \*.db

Do you still have the old rings? What about the builder files? Can you post the output of

swift-ring-builder account.builder
swift-ring-builder container.builder
swift-ring-builder object.builder

Another idea; you might try removing swauth from the pipeline and adding an overlapping user to tempauth:

user_mainaccount_ rameez = testing .admin

With that swift -A https://my-swift-cluster.example.com:8080/auth/v1.0 -U mainaccount:rameez -K testing stat -v might work...

Or even removing all auth from the pipeline, then most clients don't work, but it's easier to poke at with curl...