search for: ost0001_uuid

All, I''ve added a new 2.2 TB OST to my cluster easily enough, but this new disk array is meant to replace several smaller OSTs that I used to have of which were only 120 GB, 500 GB, and 700 GB. Adding an OST is easy, but how do I REMOVE the small OSTs that I no longer want to be part of my cluster? Is there a command to tell luster to move all the file stripes off one of the nodes?

...1: [code] [root at lustreclient1 lustre]# lfs df -h UUID bytes Used Available Use% Mounted on lustre-MDT0000_UUID 4.5G 274.3M 3.9G 6% /mnt/lustre[MDT:0] lustre-OST0000_UUID 5.9G 276.1M 5.3G 5% /mnt/lustre[OST:0] lustre-OST0001_UUID 5.9G 276.1M 5.3G 5% /mnt/lustre[OST:1] lustre-OST0002_UUID 5.9G 276.1M 5.3G 5% /mnt/lustre[OST:2] lustre-OST0003_UUID 5.9G 276.1M 5.3G 5% /mnt/lustre[OST:3] lustre-OST0004_UUID 5.9G 276.1M 5.3G 5% /mnt/lustre...

...Client1: [code] [root at lustreclient1 lustre]# lfs df -h UUID bytes Used Available Use% Mounted on lustre-MDT0000_UUID 4.5G 274.3M 3.9G 6% /mnt/lustre[MDT:0] lustre-OST0000_UUID 5.9G 276.1M 5.3G 5% /mnt/lustre[OST:0] lustre-OST0001_UUID 5.9G 276.1M 5.3G 5% /mnt/lustre[OST:1] lustre-OST0002_UUID 5.9G 276.1M 5.3G 5% /mnt/lustre[OST:2] lustre-OST0003_UUID 5.9G 276.1M 5.3G 5% /mnt/lustre[OST:3] lustre-OST0004_UUID 5.9G 276.1M 5.3G 5% /mnt/lustre[OS...

...there are a lot of free space both on OSTs and MDS: [client]$ lfs df -h UUID bytes Used Available Use% Mounted on lustre-MDT0000_UUID 43.8G 813.4M 40.5G 1% /mnt/lustre[MDT:0] lustre-OST0000_UUID 867.7G 45.8G 777.8G 5% /mnt/lustre[OST:0] lustre-OST0001_UUID 916.9G 44.9G 825.4G 4% /mnt/lustre[OST:1] lustre-OST0002_UUID 916.9G 44.9G 825.5G 4% /mnt/lustre[OST:2] lustre-OST0003_UUID 916.9G 44.9G 825.4G 4% /mnt/lustre[OST:3] lustre-OST0004_UUID 916.9G 44.9G 825.4G 4% /mnt/lustre[OST:4] lustre-OST0005_...

Hi everyone, I have seen this question here before, but without a very satisfactory answer. One of our half a dozen clients has lost access to a set of OSTs: > lfs osts OBDS:: 0: lustre-OST0000_UUID ACTIVE 1: lustre-OST0001_UUID ACTIVE 2: lustre-OST0002_UUID INACTIVE 3: lustre-OST0003_UUID INACTIVE 4: lustre-OST0004_UUID INACTIVE 5: lustre-OST0005_UUID ACTIVE 6: lustre-OST0006_UUID ACTIVE All OSTs show as completely fine on the other clients, and the system is working there. In addition, I have run numerous checks of the...

...if I run lfs df -i i get: UUID Inodes IUsed IFree I Use% Mounted on cetafs-MDT0000_UUID 975470592 20949223 954521369 2% /mnt/data[MDT:0] cetafs-OST0000_UUID 19073280 17822213 1251067 93% /mnt/data[OST:0] cetafs-OST0001_UUID 19073280 17822532 1250748 93% /mnt/data[OST:1] cetafs-OST0002_UUID 19073280 17822560 1250720 93% /mnt/data[OST:2] cetafs-OST0003_UUID 19073280 17822622 1250658 93% /mnt/data[OST:3] cetafs-OST0004_UUID 19073280 17822181 1251099 93% /mnt/data[OST:4]...

...before failing recovery. We performed that experiment on our test lustre installation with one OST. storage02 is our OSS [root at storage02 ~]# lctl dl 0 UP mgc MGC10.143.245.3 at tcp 31259d9b-e655-cdc4-c760-45d3df426d86 5 1 UP ost OSS OSS_uuid 3 2 UP obdfilter home-md-OST0001 home-md-OST0001_UUID 7 [root at storage02 ~]# lctl --device 2 set_timeout 600 set_timeout has been deprecated. Use conf_param instead. e.g. conf_param lustre-MDT0000 obd_timeout=50 usage: conf_param obd_timeout=<secs> run <command> after connecting to device <devno> --device <devno> <command...

Hi, We run four-node Lustre 2.3, and I needed to both change hardware under MGS/MDS and reassign an OSS ip. Just the same, I added a brand new 10GE network to the system, which was the reason for MDS hardware change. I ran tunefs.lustre --writeconf as per chapter 14.4 in Lustre Manual, and everything mounts fine. Log regeneration apparently works, since it seems to do something, but

...anyone else seeing this? seems weird that 1.6.3 has been out there for a while and nobody else has reported it, but I can''t think or any more testing variants I can try... anyway, some more simple setup info: % lfs getstripe /mnt/testfs/ OBDS: 0: testfs-OST0000_UUID ACTIVE 1: testfs-OST0001_UUID ACTIVE /mnt/testfs/ default stripe_count: -1 stripe_size: 1048576 stripe_offset: -1 /mnt/testfs/blah obdidx objid objid group 1 3 0x3 0 0 2 0x2 0 %...

Hello, I''ve several problems with quota on our testcluster: When I set the quota for a person to a given value (e.g. the values which are provided in the operations manual), I''m able to write exact the amount which is set with setquota. But when I delete the files(file) I''m not able to use this space again. Here is what I''ve done in detail: lfs checkquota

...B> I deactivated those two OSTs below. [root at mgs data]# lfs df -h UUID bytes Used Available Use% Mounted on AC3-MDT0000_UUID 37.5G 499.5M 34.5G 1% /data[MDT:0] AC3-OST0000_UUID 16.4T 2.2T 13.3T 14% /data[OST:0] AC3-OST0001_UUID 16.4T 1.8T 13.7T 12% /data[OST:1] AC3-OST0002_UUID 6.4T 6.0T 49.2G 99% /data[OST:2] AC3-OST0003_UUID 6.4T 6.1T 912.9M 100% /data[OST:3] AC3-OST0004_UUID 4.3T 4.1T 17.2G 100% /data[OST:4] AC3-OST0005_UUID...