Hi listers,
On a SLES8 guest we have found that file /var/log/lastlog is reported to
be 26G. Also the /var/log/faillog is reported to be 2G. But, the /var is
located on a 3390 model 3. So that disk, that also contains other
directories, is only 2.3 G. Command df shows that the / is 83% in use.
Hello Donald,
We recently added a feature that allows to add kernel parameters at boot
time. On RHEL5.4 you probably can use:
#CP IPL devno parm s
or
#CP IPL devno parm single
To start your system in single user mode.
Best Regards
Michael
On Mon, 2010-07-12 at 09:46 -0700, Donald Russell
On Wednesday 21 July 2010 05:03, van Sleeuwen, Berry wrote:
On a SLES8 guest we have found that file /var/log/lastlog is reported to
be 26G. Also the /var/log/faillog is reported to be 2G. But, the /var is
located on a 3390 model 3. So that disk, that also contains other
directories, is only 2.3
Hello Edmund,
Sparse files. OK. Then the next question, how can I store a 26G file in
a machine that isn't that large? And to add to this, why does the
filesystem backup really dump 26G into our TSM server?
So it looks like the data is going somewhere.
Berry.
Op 21-07-10 15:41, Edmund R.
RSYNC is your friend.
rsync -a -S sourcedir/. targetdir/.
where -S means handle sparse files intelligently. TAR also has an
option for handling sparse files.
-- R;
On Wed, Jul 21, 2010 at 11:59, Berry van Sleeuwen
berry.vansleeu...@xs4all.nl wrote:
Hello Edmund,
Sparse
On Wednesday 21 July 2010 11:59, Berry van Sleeuwen wrote:
Sparse files. OK. Then the next question, how can I store a 26G file in
a machine that isn't that large? And to add to this, why does the
filesystem backup really dump 26G into our TSM server?
Because it isn't really using 26GB of disk
Sparse files. OK. Then the next question, how can I store a 26G file in
a machine that isn't that large?
Because sparse files are just a bunch of pointers -- the data doesn't really
exist. It's just diddling around with the directory inode.
And to add to this, why does the
filesystem backup
We have a z10 running VM 5.4 in LPAR #1.
The box has 2 half speed CP's, 2 IFL's, and 2 ZAAP's.
We want to modify a specific zLinux guest, call it zLinux1, to only run on the
IFL's.
So far, we can get it to see all 6 engines which is not good.
Sorry if this is obvous to some, what would be the
On 7/21/2010 at 01:21 PM, Ed Long rdhm...@prodigy.net wrote:
We have a z10 running VM 5.4 in LPAR #1.
The box has 2 half speed CP's, 2 IFL's, and 2 ZAAP's.
We want to modify a specific zLinux guest, call it zLinux1, to only run on
the IFL's.
So far, we can get it to see all 6 engines which
Thanks for thinking about our problem.
So does your construct
COMMAND DEFINE CPU 00 IFL
effectively tell VM to assign the first real IFL to this VM as CPU 00? On our
system, the first real IFL is CPU 02 (00 and 01 are the CP's).
Edward Long
--- On Wed, 7/21/10, Mark Post mp...@novell.com
On 7/21/2010 at 05:16 PM, Ed Long rdhm...@prodigy.net wrote:
Thanks for thinking about our problem.
So does your construct
COMMAND DEFINE CPU 00 IFL
effectively tell VM to assign the first real IFL to this VM as CPU 00?
No. This is referring to the virtual CPUs that the guest will
Thank you all for your replies. It's clear to me, we were dumping zero's.
Regards, Berry.
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390
Does that imply then that a TMC backed up sparse file could not be
restored to the same device it came off of? Would TMC attempt to restore
all 26G?
On 07/21/2010 12:14 PM, David Boyes wrote:
Sparse files. OK. Then the next question, how can I store a 26G file in
a machine that isn't that
On Wednesday 21 July 2010 17:48, Dave Jones wrote:
Does that imply then that a TMC backed up sparse file could not be
restored to the same device it came off of? Would TMC attempt to restore
all 26G?
I would expect so. If it doesn't know enough to preserve the sparseness of a
file as it backs
I might just add that despite it's manpage assertion, rsync isn't too
intelligent about it at all.
My (non z) testing indicated that if you re-use the same target file, after
the initial run cp is significantly more efficient. The initial run for
both is comparable as the target needs to be
What's compression set to? I know that has other implications, also. Look
at the makesparsefile option for restore.
Tivoli Storage Manager backs up a sparse file as a regular file if client
compression is off. Set the compression option to yes to enable file
compression when backing up sparse
Seems Jim couldn't keep the lid on things.
The IBM Canada home page is all dressed up with nowhere to go ... :0)
Shane ...
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to
k'
Dear friend:
how are you ?h0
Just received my iphone 3gs 32gb from this website www.iebay.80.hkj. much
cheaper than others and genuine . if you would like to get one,you can check it
out,
all the best for 2010
Regardsplanted in5E
18 matches
Mail list logo
