Hi folks,
I am member of Solaris Install team and I am currently working
on making Slim installer compliant with ZFS boot design specification:
http://opensolaris.org/os/community/arc/caselog/2006/370/commitment-materials/spec-txt/
After ZFS boot project was integrated into Nevada and support
Hi Lori,
Lori Alt wrote:
Richard Elling wrote:
Hi Jan, comments below...
jan damborsky wrote:
Hi folks,
I am member of Solaris Install team and I am currently working
on making Slim installer compliant with ZFS boot design specification:
http://opensolaris.org/os/community/arc
Thank you very much all for this valuable input.
Based on the collected information, I would take
following approach as far as calculating size of
swap and dump devices on ZFS volumes in Caiman
installer is concerned.
[1] Following formula would be used for calculating
swap and dump sizes:
Hi Darren,
Darren J Moffat wrote:
Jan Damborsky wrote:
Thank you very much all for this valuable input.
Based on the collected information, I would take
following approach as far as calculating size of
swap and dump devices on ZFS volumes in Caiman
installer is concerned.
[1] Following
Darren J Moffat wrote:
jan damborsky wrote:
I think it is necessary to have some absolute minimum
and not allow installer to proceed if user doesn't
provide at least minimum required, as we have to make
sure that installation doesn't fail because of space
issues.
I very strongly disagree
Hi Mike,
Mike Gerdts wrote:
On Wed, Jun 25, 2008 at 11:09 PM, Jan Damborsky [EMAIL PROTECTED] wrote:
Thank you very much all for this valuable input.
Based on the collected information, I would take
following approach as far as calculating size of
swap and dump devices on ZFS volumes
Hi Jeff,
Jeff Bonwick wrote:
Neither swap or dump are mandatory for running Solaris.
Dump is mandatory in the sense that losing crash dumps is criminal.
I think that installer should be tolerant in this point and shouldn't
refuse to proceed with installation if user doesn't provide enough
Mike Gerdts wrote:
On Mon, Jun 30, 2008 at 9:19 AM, jan damborsky [EMAIL PROTECTED] wrote:
Hi Mike,
Mike Gerdts wrote:
On Wed, Jun 25, 2008 at 11:09 PM, Jan Damborsky [EMAIL PROTECTED]
wrote:
Thank you very much all for this valuable input.
Based on the collected information, I would
Dave Miner wrote:
I agree - I am just thinking, if it is fine in general to allow
normal non-experienced user (who is the target audience for Slim
installer) to run system without swap. To be honest, I don't know,
since I am not very experienced in this area.
If people agree that this is not
Hi all,
Based on the further comments I received, following
approach would be taken as far as calculating default
size of swap and dump devices on ZFS volumes in Caiman
installer is concerned.
[1] Following formula would be used for calculating
swap and dump sizes:
size_of_swap = MAX(512
Dave Miner wrote:
jan damborsky wrote:
...
[2] dump and swap devices will be considered optional
dump and swap devices will be considered optional during
fresh installation and will be created only if there is
appropriate space available on disk provided.
Minimum disk space required
Jeff Bonwick wrote:
To be honest, it is not quite clear to me, how we might utilize
dumpadm(1M) to help us to calculate/recommend size of dump device.
Could you please elaborate more on this ?
dumpadm(1M) -c specifies the dump content, which can be kernel, kernel plus
current process, or all
Hi Robert,
you are quite welcome !
Thank you very much for your comments.
Jan
Robert Milkowski wrote:
Hello jan,
Tuesday, July 1, 2008, 11:09:54 AM, you wrote:
jd Hi all,
jd Based on the further comments I received, following
jd approach would be taken as far as calculating default
Hi ZFS team,
I am currently working on fixes for couple of bugs in OpenSolaris Caiman
installer and since they are related to the ZFS, I would like to kindly
ask you, if you could please help me to understand, if the issues
encountered and mentioned below are known (somebody works on them or
if
. Then you can test
for the value of the parameter and know if it was a failed install.
John
On Mon, Aug 18, 2008 at 11:04 AM, Jan Damborsky [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
Hi ZFS team,
I am currently working on fixes for couple of bugs in OpenSolaris
Caiman
Hi Darren,
thank you very much for your help.
Please see my comments below.
Jan
Darren J Moffat wrote:
jan damborsky wrote:
Hi John,
I like this idea - it would be clear solution for the problem.
Is it possible to manage custom parameters with standard CLI
commands (these are used
Hi Andrew,
this is what I am thinking about based on John's
and Darren's responses.
I will file RFE for having possibility to set user
properties for pools (if it doesn't already exist).
Thank you,
Jan
andrew wrote:
Perhaps user properties on pools would be useful here? At present only ZFS
Darren J Moffat wrote:
jan damborsky wrote:
zfs set caiman:install=preparing rpool/ROOT
That sounds reasonable. It is not atomic operation from installer
point of view, but the time window is really short (installer can
set ZFS user property almost immediately after pool is created
And log an RFE for having user defined properties at the pool (if one
doesn't already exist).
6739057 was filed to track this.
Thank you,
Jan
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
Hi,
I have successfully created dedicated ZFS volume for dump
device and activated it using dumpadm(1M) command:
# zfs create -b 131072 -V 2048m data/dump
# dumpadm -n -d /dev/zvol/dsk/data/dump
Dump content: kernel pages
Dump device: /dev/zvol/dsk/data/dump (dedicated)
Savecore
Hi Mark,
Mark J Musante wrote:
On Mon, 8 Sep 2008, jan damborsky wrote:
Is there any way to release dump ZFS volume after it was activated by
dumpadm(1M) command ?
Try 'dumpadm -d swap' to point the dump to the swap device.
That helped - since swap is on ZFS volume (which can't
Hi ZFS team,
when testing installation with recent OpenSolaris builds,
we have been encountering that in some cases, people end up
in GRUB prompt after the installation - it seems that menu.lst
can't be accessed for some reason. At least two following bugs
seems to be describing the same
Hi Dick,
I am redirecting your question to zfs-discuss
mailing list, where people are more knowledgeable
about this problem and your question could be
better answered.
Best regards,
Jan
dick hoogendijk wrote:
I have s10u6 installed on my server.
zfs list (partly):
NAME
Hi Jeffrey,
jeffrey huang wrote:
Hi, Jan,
After successfully install AI on SPARC(zpool/zfs created), without
reboot, I want try a installation again, so I want to destroy the rpool.
# dumpadm -d swap -- ok
# zfs destroy rpool/dump -- ok
# swap -l
# swap -d /dev/zvol/dsk/rpool/swap --
Hi Richard,
Richard Robinson wrote:
I should add that I also used truss and saw the same ENOMEM error. I am on a
4Gb system with swap -l reporting
swapfile dev swaplo blocks free
/dev/zvol/dsk/rpool/swap 181,1 8 4194296 4194296
and I was trying to follow the directions
casper@sun.com wrote:
hi Jan (and all)
My failure was when running
# swap -d /dev/zvol/dsk/rpool/swap
I saw this in my truss output.
uadmin(16, 3, -2748781172232)Err#12 ENOMEM
That sounds like too much memory in use: can't remove swap.
It seems it also happens in
Hi ZFS guys,
when playing with one of recent version of OpenSolaris GUI installer,
I have tried to restart it after previous failure.
However, the installer failed when trying to destroy previously created
ZFS root pool. It was discovered that this is due to the fact that dump
ZFS volume could
Hi Jeffrey,
Jeffrey Huang wrote:
Hi, Jan,
δΊ 2009/12/9 20:41, Jan Damborsky ει:
# dumpadm -d swap
dumpadm: no swap devices could be configured as the dump device
# dumpadm
Dump content: kernel pages
Dump device: /dev/zvol/dsk/rpool/dump (dedicated)
Savecore directory: /var/crash
28 matches
Mail list logo
