Ah - looks like I should have read the tar output message closer myself.  :)


 -----Original Message-----
From:   Bert Wesarg [mailto:wesarg@informatik.uni-halle.de]
Sent:   Tuesday, April 24, 2007 09:12 AM Eastern Standard Time
To:     PLPA users list
Subject:        Re: [PLPA users] HMT



On Tue, 24 Apr 2007, Jeff Squyres wrote:

> On Apr 24, 2007, at 8:07 AM, Bert Wesarg wrote:
>
> >> /sys % sudo tar cjf /tmp/cpu-topology.tar.bz2 devices/system/{cpu/
> >> cpu*/topology/*,node/node*/cpu*}
> >> tar: devices/system/node/node0/cpumap: File shrank by 4093 bytes;
> >> padding with zeros
> >> tar: Error exit delayed from previous errors
> >>
> >> Hmm.  Got any ideas?
> > I think, because there is no topology dir in older kernel. from
> > this type
> > of machines i have two racks full of it but with the same old kernel.
>
> Look a little closer at that message -- the file node0/cpumap *is*
> there, but tar is getting weird data from it (it expects 4096 bytes
> but only gets 3).  Here's the output I had later in my mail:
No, No! the line should expand to the following:

devices/system/cpu/cpu*/topology/*

and

devices/system/node/node*/cpu*

and the problem lies in the topology dir, if it is not present

the problem with the file size don't matter, it should be only a warning.

>
> >> /sys/devices/system/node/node0 % cat cpumap
> >> ff
>
> It corresponds to the 3 bytes that tar assumedly was able to get (2
> f's + \n).
>
> So I'm not sure that tar'ing up these directories will work as
> expected -- even with a kernel that provides all the information that
> we're looking for.
i attached the tar from a dual-socket dual-core amd64 machine. the tar
output was this:

tar: devices/system/cpu/cpu0/topology/core_id: File shrank by 4094 bytes; padding with zeros
tar: devices/system/cpu/cpu0/topology/core_siblings: File shrank by 4087 bytes; padding with zeros
tar: devices/system/cpu/cpu0/topology/physical_package_id: File shrank by 4094 bytes; padding with zeros
tar: devices/system/cpu/cpu0/topology/thread_siblings: File shrank by 4087 bytes; padding with zeros
tar: devices/system/cpu/cpu1/topology/core_id: File shrank by 4094 bytes; padding with zeros
tar: devices/system/cpu/cpu1/topology/core_siblings: File shrank by 4087 bytes; padding with zeros
tar: devices/system/cpu/cpu1/topology/physical_package_id: File shrank by 4094 bytes; padding with zeros
tar: devices/system/cpu/cpu1/topology/thread_siblings: File shrank by 4087 bytes; padding with zeros
tar: devices/system/cpu/cpu2/topology/core_id: File shrank by 4094 bytes; padding with zeros
tar: devices/system/cpu/cpu2/topology/core_siblings: File shrank by 4087 bytes; padding with zeros
tar: devices/system/cpu/cpu2/topology/physical_package_id: File shrank by 4094 bytes; padding with zeros
tar: devices/system/cpu/cpu2/topology/thread_siblings: File shrank by 4087 bytes; padding with zeros
tar: devices/system/cpu/cpu3/topology/core_id: File shrank by 4094 bytes; padding with zeros
tar: devices/system/cpu/cpu3/topology/core_siblings: File shrank by 4087 bytes; padding with zeros
tar: devices/system/cpu/cpu3/topology/physical_package_id: File shrank by 4094 bytes; padding with zeros
tar: devices/system/cpu/cpu3/topology/thread_siblings: File shrank by 4087 bytes; padding with zeros
tar: devices/system/node/node0/cpumap: File shrank by 4087 bytes; padding with zeros
tar: devices/system/node/node1/cpumap: File shrank by 4087 bytes; padding with zeros

Bert