Thanks. Can you tell me how to do the mapping back to the MDS inode?
For example, is 1162976 in the list below the MDS inode? May as well look.
I am following the directions in the recent threads to redo the OSTs
(not the whole Lustre file system). I will restore the indicated files.
bob
O
On 2010-11-30, at 12:14, Lukas Hejtmanek wrote:
> I see some oddities on Lustre clients running under Xen DomU ...
> when the DomU is being suspended (most memory and CPU is stolen by another
> DomU).
>
> Is this something known or unsupported? (I.e., running Lustre under Xen with
> domains pree
On 2010-11-30, at 11:17, Bob Ball wrote:
> [r...@umdist03 d0]# ls -l
> total 182976
> -rw-rw-rw- 1 daits users 45002956 Jul 5 20:52 1162976
> -rw-rw-rw- 1 daits users 44569036 Jul 7 02:53 1200608
> -rw-rw-rw- 1 daits users 49108913 Jun 28 04:43 1218976
> -rw-rw-rw- 1 daits users 48658429 Jul 16 1
Hello,
I see some oddities on Lustre clients running under Xen DomU. I got messages
like this:
Jul 29 14:35:23 quark8-1 kernel: Lustre: Request x2674628 sent from
stable-OST0001-osc-8801a72a5000 to NID 147.251@tcp 100s ago has
timed out (limit 100s).
Jul 29 14:35:23 quark8-1 kernel: Lustre
OK, well, that file was just not anywhere, and it was only 1. But now
that the OST is "completely empty", I find that it is not really empty.
For example:
[r...@umdist03 d0]# pwd
/mnt/ost/O/0/d0
[r...@umdist03 d0]# ls -l
total 182976
-rw-rw-rw- 1 daits users 45002956 Jul 5 20:52 1162976
-rw-
OK, thanks. Scary, to see errors out of lfs find.
bob
On 11/30/2010 1:47 AM, Andreas Dilger wrote:
> On 2010-11-29, at 20:18, Bob Ball wrote:
>> I have an odd problem. I am trying to empty all files from a set of OST
>> as indicated below, by making a list via lfs find and then sending that
>>
