I am emptying a set of OST so that I can reformat the underlying RAID-6
more efficiently. Two questions:
1. Is there a quick way to tell if the OST is really empty? lfs_find
takes many hours to run.
2. When I reformat, I want it to retain the same ID so as to not make
holes in the list. From
On 6 Nov 2010, at 14:24, Bob Ball wrote:
I am emptying a set of OST so that I can reformat the underlying RAID-6
more efficiently. Two questions:
1. Is there a quick way to tell if the OST is really empty? lfs_find
takes many hours to run.
lfs df -i from a client or simply df -i from
On 11/06/2010 10:24 AM, Bob Ball wrote:
I am emptying a set of OST so that I can reformat the underlying RAID-6
more efficiently. Two questions:
1. Is there a quick way to tell if the OST is really empty? lfs_find
takes many hours to run.
Yes ...
df -H /path/to/OST/mount_point
if
Responding to everyone (and thanks to all)
lfs df -i from a client or simply df -i from the OSS node ...
This still shows of order 100 inodes after the OST was emptied.
tunefs.lustre --print /dev/sdj will tell you the index in base 10.
Yes, this worked.
df -H /path/to/OST/mount_point
This
On 6 Nov 2010, at 19:28, Bob Ball wrote:
I intend to be VERY careful with this. Thank you all. Any further
advice before I do this, likely on Monday, will be greatly appreciated.
I believe it is possible to use udev to assign device names to devices which
would make the pathname both
