Hi Everybody, I have some problems in solaris 10 installation. After installing the first CD , I removed the CD from CDrom , after that the machine is getting rebooting again and again. It is not asking second CD to install. If you have any idea. Please tell me. Thanks & Regards Masthan __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20061211/00aca98f/attachment.html>
install-discuss at opensolaris.org looks like the more appropriate list to post questions like yours. dudekula mastan wrote:> Hi Everybody, > > I have some problems in solaris 10 installation. > > After installing the first CD , I removed the CD from CDrom , after that the machine is getting rebooting again and again. It is not asking second CD to install. > > If you have any idea. Please tell me. > > Thanks & Regards > Masthan >-- Zoram Thanga::Sun Cluster Development::http://blogs.sun.com/zoram
dudekula mastan
2006-Dec-12 10:13 UTC
[zfs-discuss] Need Clarification on ZFS quota property.
Hi All, Assume the device c0t0d0 size is 100000 KB. I created ZFS file system on this $ zpool create -f mypool c0t0d0s2 and to limit the size of ZFS file system I used quota property. $ zfs set quota = 5000K mypool Which 5000 K bytes are belongs (or reserved) to mypool first 5000KB or last 5000KB or random ? UFS and VxFS file systems have options to limit the size of file system on the device (E.g. We can limit the size offrom 1 block to some nth block . Like this is there any sub command to limit the size of ZFS file system from 1 block to some n th block ? Your help is appreciated. Thanks & Regards Masthan __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20061212/4a2df980/attachment.html>
On 12 December, 2006 - dudekula mastan sent me these 2,7K bytes:> > Hi All, > > Assume the device c0t0d0 size is 100000 KB. > > I created ZFS file system on this > > $ zpool create -f mypool c0t0d0s2 > > and to limit the size of ZFS file system I used quota property. > > $ zfs set quota = 5000K mypool > > Which 5000 K bytes are belongs (or reserved) to mypool first 5000KB or last 5000KB or random ?"random".. When you''ve stored 5000K, you can''t store anymore there.> UFS and VxFS file systems have options to limit the size of file > system on the device (E.g. We can limit the size offrom 1 block to > some nth block . Like this is there any sub command to limit the > size of ZFS file system from 1 block to some n th block ?Just amount, not specific positions on/portions of the FS/devices. /Tomas -- Tomas ?gren, stric at acc.umu.se, http://www.acc.umu.se/~stric/ |- Student at Computing Science, University of Ume? `- Sysadmin at {cs,acc}.umu.se
Darren Dunham
2006-Dec-12 18:01 UTC
[zfs-discuss] Need Clarification on ZFS quota property.
> Hi All, > > Assume the device c0t0d0 size is 100000 KB. > I created ZFS file system on this > $ zpool create -f mypool c0t0d0s2This creates a pool on the entire slice.> and to limit the size of ZFS file system I used quota property. > > $ zfs set quota = 5000K mypoolNote that this sets a quota only on the default filesystem that was created along with the zpool. There may be other filesystems created on the pool with different quotas. You are not setting a quota on the pool itself.> Which 5000 K bytes are belongs (or reserved) to mypool first 5000KB > or last 5000KB or random ?All blocks belong to the pool. The /mypool filesystem may be allocated any particular space there depending on other filesystems and layout. Attempts to allocate space greater than 5000K will fail.> UFS and VxFS file systems have options to limit the size of file > system on the device (E.g. We can limit the size offrom 1 block to > some nth block . Like this is there any sub command to limit the > size of ZFS file system from 1 block to some n th block ?I''m not sure what you''re saying here. UFS and VxFS normally take the entire space of a disk slice or volume. The pool creation does the same thing. Can you clarify what you mean by limiting the size of UFS or VxVS? -- Darren Dunham ddunham at taos.com Senior Technical Consultant TAOS http://www.taos.com/ Got some Dr Pepper? San Francisco, CA bay area < This line left intentionally blank to confuse you. >
dudekula mastan
2006-Dec-13 10:51 UTC
[zfs-discuss] Need Clarification on ZFS quota property.
Hi Darren Thanks for your reply. You please take a deep look into the following command: $mkfs -F vxfs -o bsize=1024 /dev/rdsk/c5t20d9s2 2048000 The above command creates vxfs file system on first 2048000 blocks (each block size is 1024 bytes) of /dev/rdsk/c5t20d9s2 . Like this is there a option to limit the size of ZFS file system.? if so what it is ? how it is ? Your help is appreciated. Thanks & Regards Masthan Darren Dunham <ddunham at taos.com> wrote: > Hi All,> > Assume the device c0t0d0 size is 100000 KB. > I created ZFS file system on this > $ zpool create -f mypool c0t0d0s2This creates a pool on the entire slice.> and to limit the size of ZFS file system I used quota property. > > $ zfs set quota = 5000K mypoolNote that this sets a quota only on the default filesystem that was created along with the zpool. There may be other filesystems created on the pool with different quotas. You are not setting a quota on the pool itself.> Which 5000 K bytes are belongs (or reserved) to mypool first 5000KB > or last 5000KB or random ?All blocks belong to the pool. The /mypool filesystem may be allocated any particular space there depending on other filesystems and layout. Attempts to allocate space greater than 5000K will fail.> UFS and VxFS file systems have options to limit the size of file > system on the device (E.g. We can limit the size offrom 1 block to > some nth block . Like this is there any sub command to limit the > size of ZFS file system from 1 block to some n th block ?I''m not sure what you''re saying here. UFS and VxFS normally take the entire space of a disk slice or volume. The pool creation does the same thing. Can you clarify what you mean by limiting the size of UFS or VxVS? -- Darren Dunham ddunham at taos.com Senior Technical Consultant TAOS http://www.taos.com/ Got some Dr Pepper? San Francisco, CA bay area < This line left intentionally blank to confuse you. > _______________________________________________ zfs-discuss mailing list zfs-discuss at opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss --------------------------------- Need a quick answer? Get one in minutes from people who know. Ask your question on Yahoo! Answers. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20061213/af256129/attachment.html>
Darren Dunham
2006-Dec-13 16:08 UTC
[zfs-discuss] Need Clarification on ZFS quota property.
> $mkfs -F vxfs -o bsize=1024 /dev/rdsk/c5t20d9s2 2048000 > > The above command creates vxfs file system on first 2048000 blocks (each block size is 1024 bytes) of /dev/rdsk/c5t20d9s2 . > > Like this is there a option to limit the size of ZFS file system.? if > so what it is ? how it is ?No, there''s nothing similar. Space is managed at a pool level. Writes by any filesystem may occur anywhere in the pool. Can I ask why this would be useful to you? What can you accomplish by limiting the filesystem to a particular location? There might be alternatives. -- Darren Dunham ddunham at taos.com Senior Technical Consultant TAOS http://www.taos.com/ Got some Dr Pepper? San Francisco, CA bay area < This line left intentionally blank to confuse you. >
Craig Morgan
2006-Dec-13 17:14 UTC
[zfs-discuss] Need Clarification on ZFS quota property.
This is probably an attempt to ''short-stroke'' a larger disk with the intention utilising only a small ammount of the disk surface, as a technique it used to be quite common for certain apps (notably DBs). Hence you saw deployments of quite large disks but with perhaps only 1/4-1/2 physical utilisation. As the industry has moved toward HW RAID, its less prevalent, but still has some merits on occassion. Craig On 13 Dec 2006, at 16:08, Darren Dunham wrote:>> $mkfs -F vxfs -o bsize=1024 /dev/rdsk/c5t20d9s2 2048000 >> >> The above command creates vxfs file system on first 2048000 >> blocks (each block size is 1024 bytes) of /dev/rdsk/c5t20d9s2 . >> >> Like this is there a option to limit the size of ZFS file system.? if >> so what it is ? how it is ? > > No, there''s nothing similar. > > Space is managed at a pool level. Writes by any filesystem may occur > anywhere in the pool. > > Can I ask why this would be useful to you? What can you accomplish by > limiting the filesystem to a particular location? There might be > alternatives. > > -- > Darren Dunham > ddunham at taos.com > Senior Technical Consultant TAOS http:// > www.taos.com/ > Got some Dr Pepper? San Francisco, CA bay > area > < This line left intentionally blank to confuse you. > > _______________________________________________ > zfs-discuss mailing list > zfs-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Darren Dunham
2006-Dec-13 17:45 UTC
[zfs-discuss] Need Clarification on ZFS quota property.
> This is probably an attempt to ''short-stroke'' a larger disk with the > intention utilising only a small ammount of the disk surface, as a > technique it used to be quite common for certain apps (notably DBs). > Hence you saw deployments of quite large disks but with perhaps only > 1/4-1/2 physical utilisation.I guess I was assuming something else was going on. Doing the above just is pretty easy by simply limiting the entire pool to that area (slices) rather than limiting the filesystem. -- Darren Dunham ddunham at taos.com Senior Technical Consultant TAOS http://www.taos.com/ Got some Dr Pepper? San Francisco, CA bay area < This line left intentionally blank to confuse you. >