Extent DB

After reading a lot in the docs I did'nt find an answer and try to get an answer here. I have an IDS10 with one dbspace on a single disk with one database in it. What can I do if the disk is full ? As far as I know I can't resize a dbspace nor span a dbspace on more disks ? Is that true ? And what can I do I think I have one more month until I will this problem :-) Freudi

Hi, This is easy to solve (in case you have a new disk or set of disks available). You have to add a chunk to the existing dbspace and IDS will use the new space after a level 0 backup and switch of the logical log (you should execute onmode -l and save the log after adding the device to make sure it is protocolled). I assume you have a raw device as your dbspace device. (not much difference if you use a cooked file) Syntax is: onspaces -a <dbspacename> -p <path> -o <offset> -s <size> E.g. onspaces -a rootdbs -p /dev/rdsk/c0t10d0s10 -o 100 -s 10000000This would add another 10 GB to the rootdbs chunk on the named device (should be a partition name, here for solaris, adjust for your OS). The offset is chosen to prevent overwriting the partition table. In case you are using cooked files, replace /dev/rdsk by the filename and set offset 0. Hope this helps, Marcus -----Original Message----- From: MICHAEL MEIER [mailto:freudi_t@yahoo.de] Sent: Tuesday, December 11, 2007 1:09 PM To: ids@iiug.org Subject: Extent DB [10684] After reading a lot in the docs I did'nt find an answer and try to get an answer here. I have an IDS10 with one dbspace on a single disk with one database in it. What can I do if the disk is full ? As far as I know I can't resize a dbspace nor span a dbspace on more disks ? Is that true ? And what can I do I think I have one more month until I will this problem :-) Freudi ************************************************************************ ******* Forum Note: Use "Reply" to post a response in the discussion forum.

Thanks for the quick response. Sounds easy. I thought I haven't to read anything about chunks because I won't use them. So a kind of order is Disk1->chunk->dbspace->DB Disk2->Chunk^ I think I got this. Why I have to do a a Level 0 backup if add space ? I use the disk as raw devices, thats why I did'nt add an offset. Is this OK for a raw device ? Freudi

I believe you can mount a new dbspace on another physical disk then you can reorg tables to that new dbspace, or simply add extents in the new dbspace. But even if that did not work and I think it will, you could put a symbolic link between a new directory and the new empty disk. Then mount a dbspace on the cooked directory. But again I would suggest mounting a raw dbspace on the new disk as I suggested above. On Dec 11, 2007, at 7:09 AM, MICHAEL MEIER wrote: > After reading a lot in the docs I did'nt find an answer and try to > get an > answer here. I have an IDS10 with one dbspace on a single disk with > one > database in it. > What can I do if the disk is full ? As far as I know I can't resize > a dbspace > nor span a dbspace on more disks ? Is that true ? And what can I do > I think I > have one more month until I will this problem :-) > > Freudi > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. >

Sorry but I'm useing 4GL since 15 years but I'm new to the online engine. Does extents mean chunks or is something different ? What you mean with reorg tables ? Moving a table from the old dbspace to the new one? I guess that is something what I do for performance reason. But if I had'nt problems with the performance. I just want to add space for a db. And it would be nice if the IDS simply use it when the user adds data, no matter in in which table this new data lies. Freudi

YOu picked up on a mistake I made. I do is but do not have the terms correct. Where I said dbspace I should have said chunk. Rather than confuse you more I suggest reading these sections in IBM Informix Dynamic Server Admin Guide Version 10.0 On Page 1-5 Allocating DIsk Space On page 10.4 Disk allocation of chunks Actually all of chapter 10 is on target Sorry I confused terms On Dec 11, 2007, at 8:53 AM, MICHAEL MEIER wrote: > Sorry but I'm useing 4GL since 15 years but I'm new to the online > engine. > Does extents mean chunks or is something different ? > What you mean with reorg tables ? Moving a table from the old > dbspace to the > new one? I guess that is something what I do for performance reason. > But if I > had'nt problems with the performance. I just want to add space for a > db. And > it would be nice if the IDS simply use it when the user adds data, > no matter > in in which table this new data lies. > > Freudi > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. >

Hi, Setting an offset is recommended on certain platforms when using raw devices to prevent overwriting the first block of the device which contains the partition table. It is not a real problem if you offset a chunk by 100 KB, but it can be a problem in case you move the chunk to another disk and there it is the first partition ... Personally, I offset all chunks with 100 KB, not depending on where they are located. Marcus -----Original Message----- From: MICHAEL MEIER [mailto:freudi_t@yahoo.de] Sent: Tuesday, December 11, 2007 1:50 PM To: ids@iiug.org Subject: Re: RE: Extent DB [10687] Thanks for the quick response. Sounds easy. I thought I haven't to read anything about chunks because I won't use them. So a kind of order is Disk1->chunk->dbspace->DB Disk2->Chunk^ I think I got this. Why I have to do a a Level 0 backup if add space ? I use the disk as raw devices, thats why I did'nt add an offset. Is this OK for a raw device ? Freudi ************************************************************************ ******* Forum Note: Use "Reply" to post a response in the discussion forum.

I will read a bit more. The key answer came from Marcus. After reading a lot I thought: Disk->DbSpace->Chunk but now I think Disk->chunk->DbSpace Thanks for helping Freudi

That make sense. So it is possible to move a chunk from on raw hd to another ? Did'nt read that either :-)

Hello, Yes, the move is an operating system dependent function. Works fine under AIX even with the DB operational. "MICHAEL MEIER" <freudi_t@yahoo.de> Sent by: ids-bounces@iiug.org 11/12/2007 16:13 Please respond to ids@iiug.org To ids@iiug.org cc Subject Re: RE: Re: RE: Extent DB [10695] That make sense. So it is possible to move a chunk from on raw hd to another ? Did'nt read that either :-) ******************************************************************************* Forum Note: Use "Reply" to post a response in the discussion forum.

Yes! suppose your raw chunk is in /dev/hda2 dd if=/dev/hda2 of=/ifmx_data/my_chunk bs=1024k more info about 'dd" : man dd But... - IDS must be taken off line before... - Your IDS must use links to your chunks - Need to re-link the new patch. - Remember you do not more work with KAIO VPs, so review the AIO VPs on ONCONFIG _______________________________________ Existem 10 tipos de pessoas no mundo, aqueles que compreendem binário e aqueles que não ----- Mensagem original ---- De: MICHAEL MEIER <freudi_t@yahoo.de> Para: ids@iiug.org Enviadas: Terça-feira, 11 de Dezembro de 2007 15:13:43 Assunto: Re: RE: Re: RE: Extent DB [10695] That make sense. So it is possible to move a chunk from on raw hd to another ? Did'nt read that either :-) ******************************************************************************* Forum Note: Use "Reply" to post a response in the discussion forum. Abra sua conta no Yahoo! Mail, o único sem limite de espaço para armazenamento! http://br.mail.yahoo.com/

sorry.. I post how move from a Raw to cooked file... now, answering your question, yes... you can move from HD to another too.. with the same command.. dd if=/dev/hda2 of=/dev/hdb1 In this case: - IDS must be taken off line before... - Your IDS must use links to your chunks - Need to re-link the new patch. - This is only If you use offset = 0 and don't have another chunks (with offset > 0) on the same partition. Another way to do this with mirror chunks.... 1) create a mirror chunk in another HD or filesystem 2) put the primary chunk off-line.. (onspaces -s ) 3) relink the path of the primary chunk to new HD ( ln -s ) 4) put the primary chunk on-line (onspaces -s ) 5) remove the mirror.. (onspaces -r ) Remember, In all cases you need have your paths with links... In all cases, if you work with offset > 0 , this can be a trouble... _______________________________________ Existem 10 tipos de pessoas no mundo, aqueles que compreendem binário e aqueles que não ----- Mensagem original ---- De: Cesar Inacio Martins <cesar_inacio_martins@yahoo.com.br> Para: ids@iiug.org Enviadas: Terça-feira, 11 de Dezembro de 2007 15:43:25 Assunto: Res: RE: Re: RE: Extent DB [10697] Yes! suppose your raw chunk is in /dev/hda2 dd if=/dev/hda2 of=/ifmx_data/my_chunk bs=1024k more info about 'dd" : man dd But... - IDS must be taken off line before... - Your IDS must use links to your chunks - Need to re-link the new patch. - Remember you do not more work with KAIO VPs, so review the AIO VPs on ONCONFIG _______________________________________ Existem 10 tipos de pessoas no mundo, aqueles que compreendem binário e aqueles que não ----- Mensagem original ---- De: MICHAEL MEIER <freudi_t@yahoo.de> Para: ids@iiug.org Enviadas: Terça-feira, 11 de Dezembro de 2007 15:13:43 Assunto: Re: RE: Re: RE: Extent DB [10695] That make sense. So it is possible to move a chunk from on raw hd to another ? Did'nt read that either :-) ******************************************************************************* Forum Note: Use "Reply" to post a response in the discussion forum. Abra sua conta no Yahoo! Mail, o único sem limite de espaço para armazenamento! http://br.mail.yahoo.com/ ******************************************************************************* Forum Note: Use "Reply" to post a response in the discussion forum. Abra sua conta no Yahoo! Mail, o único sem limite de espaço para armazenamento! http://br.mail.yahoo.com/

MICHAEL MEIER wrote: > Thanks for the quick response. Sounds easy. I thought I haven't to read > anything about chunks because I won't use them. > You're always using chunks, IDS only deals with disk as 'chunks' of space. It's just that when you create a new dbspace you assign it's initial disk chunk at the same time so you never realized it. Once a dbspace exists you can expand the dbspace by attaching more disk chunks to the dbspace. > So a kind of order is > Disk1->chunk->dbspace->DB > Disk2->Chunk^ > I think I got this. > > Why I have to do a a Level 0 backup if add space ? > You want to take a level zero archive immediately after adding the chunk so that if your system crashes you won't have to add the chunk all over again after restoring from an archive that doesn't know about it. > I use the disk as raw devices, thats why I did'nt add an offset. > Is this OK for a raw device ? > Marcus is recommending using an offset for your chunks because the disk partitioning software he uses places the partition table at the beginning of the first disk partition. So chunks defined on that first chunk REQUIRE an offset to avoid overwriting that table. He uses offsets on all chunks as a precaution in case he has to replace a crashed drive and needs to restore to a first partition a chunk that used to be on a higher numbered partition. If you are using more modern partitioning software than fdisk, it likely places the partition table in unallocated disk space at the beginning or the end of the drive/array that is walled off from the defined partitions so it is safe. Check with your Systems Administrators as to whether you need to allow offsets for the partition table (make them check if they are not sure as they don't normally worry about it making filesystems since UNIX filesystems include the offset when they are created automatically). Offsets are ONLY needed, if they are needed at all, for chunks built from RAW and COOKED device files, not for chunks defined in filesystem files. Art S. Kagel > Freudi > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > >

Wow. Links. Thats another hint. So what I did is creating a dbspace /dev/sdb. But I should ln -s /usr/informix/rawdbspace /dev/sdb and then use rawdbspace as chunk. And than I can replace or add a diefferent harddisk. Thats a nice hint. All this is not in the books or somehow hidden !! Believe me, I read a lot before I decided to post here. A last :-) question to that ln point. If I replace /dev/sdb with larger harddisk. Can I also resize, better increase, the dbspace. Or should I build a new chunk ? Freudi

Thanks Art !

Hi, Increasing the dbspace is done by adding more chunks to it. You cannot increase the size of a single chunk. The alternative of course always is to make a backup of the databases using dbexport, reinitilialize the instance on different harddisks (with links then ;) and dbimport the databases again. Marcus -----Original Message----- From: MICHAEL MEIER [mailto:freudi_t@yahoo.de] Sent: Wednesday, December 12, 2007 8:59 AM To: ids@iiug.org Subject: Re: RE: Extent DB [10708] Wow. Links. Thats another hint. So what I did is creating a dbspace /dev/sdb. But I should ln -s /usr/informix/rawdbspace /dev/sdb and then use rawdbspace as chunk. And than I can replace or add a diefferent harddisk. Thats a nice hint. All this is not in the books or somehow hidden !! Believe me, I read a lot before I decided to post here. A last :-) question to that ln point. If I replace /dev/sdb with larger harddisk. Can I also resize, better increase, the dbspace. Or should I build a new chunk ? Freudi ************************************************************************ ******* Forum Note: Use "Reply" to post a response in the discussion forum.

About Links on the manual: http://publib.boulder.ibm.com/infocenter/idshelp/v111/index.jsp?topic=/com.ibm.a dmin.doc/admin355.htm Your example this is not a good idea, because the /dev will be recreate after a reboot on your machine, and probably will lost the link /dev/sdb: ln -s /usr/informix/rawdbspace /dev/sdb The right thing to do, is create the link in a directory: ln -s /usr/informix/rawdbspace /ifmx_data/chunk_xyz. _______________________________________ Existem 10 tipos de pessoas no mundo, aqueles que compreendem binário e aqueles que não ----- Mensagem original ---- De: MICHAEL MEIER <freudi_t@yahoo.de> Para: ids@iiug.org Enviadas: Quarta-feira, 12 de Dezembro de 2007 7:58:30 Assunto: Re: RE: Extent DB [10708] Wow. Links. Thats another hint. So what I did is creating a dbspace /dev/sdb. But I should ln -s /usr/informix/rawdbspace /dev/sdb and then use rawdbspace as chunk. And than I can replace or add a diefferent harddisk. Thats a nice hint. All this is not in the books or somehow hidden !! Believe me, I read a lot before I decided to post here. A last :-) question to that ln point. If I replace /dev/sdb with larger harddisk. Can I also resize, better increase, the dbspace. Or should I build a new chunk ? Freudi ******************************************************************************* Forum Note: Use "Reply" to post a response in the discussion forum. Abra sua conta no Yahoo! Mail, o único sem limite de espaço para armazenamento! http://br.mail.yahoo.com/

MICHAEL MEIER wrote: > Wow. Links. Thats another hint. > So what I did is creating a dbspace /dev/sdb. > But I should > ln -s /usr/informix/rawdbspace /dev/sdb > and then use rawdbspace as chunk. And than I can replace or add a diefferent > harddisk. Thats a nice hint. > All this is not in the books or somehow hidden !! Believe me, I read a lot > before I decided to post here. > A last :-) question to that ln point. If I replace /dev/sdb with larger > harddisk. Can I also resize, better increase, the dbspace. Or should I build a > new chunk ? > If you relink a chuink path to a larger disk partition, it will not enlarge the chunk linked to it and you cannot expand a chunk. You CAN however add another chunk to the same or a different dbspace using the same chunk path put adding an offset to place the new chunk appended to the end of the original one expanding a dbspace that way. Art S. Kagel > Freudi > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > >

Sorry my fault.It should say ln -s /dev/sdb /usr/informix/rawdataspace This is according to the user manual. Freudi

Cesar Inacio Martins wrote: > About Links on the manual: > > http://publib.boulder.ibm.com/infocenter/idshelp/v111/index.jsp?topic=/com.ibm.a dmin.doc/admin355.htm > Your example this is not a good idea, because the /dev will be recreate after > a reboot on your machine, and probably will lost the link /dev/sdb: > ln -s /usr/informix/rawdbspace /dev/sdb > Ceasar, Symbolic links (see the -s option to ln above) will survive if the file/directory/device they point to is removed from the system or, as in the case of device files on some systems, recreated at boot time. Even hard links will survive deletion of other links, it's just that after the recreation the new entry may point to different resources than the new object. Not a problem for soft or symbolic links as they are just a small file containing the real path. Since the OS has no easy/cheap way to track down what symlinks are pointing to a given object, it doesn't try. Once the path has been recreated the link will work fine. Art S. Kagel > The right thing to do, is create the link in a directory: > ln -s /usr/informix/rawdbspace /ifmx_data/chunk_xyz. > > _______________________________________ > Existem 10 tipos de pessoas no mundo, aqueles que compreendem binário e > aqueles que não > > ----- Mensagem original ---- > De: MICHAEL MEIER <freudi_t@yahoo.de> > Para: ids@iiug.org > Enviadas: Quarta-feira, 12 de Dezembro de 2007 7:58:30 > Assunto: Re: RE: Extent DB [10708] > > Wow. Links. Thats another hint. > So what I did is creating a dbspace /dev/sdb. > But I should > ln -s /usr/informix/rawdbspace /dev/sdb > and then use rawdbspace as chunk. And than I can replace or add a > diefferent > harddisk. Thats a nice hint. > All this is not in the books or somehow hidden !! Believe me, I read a > lot > before I decided to post here. > A last :-) question to that ln point. If I replace /dev/sdb with larger > > harddisk. Can I also resize, better increase, the dbspace. Or should I > build a > new chunk ? > > Freudi > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > Abra sua conta no Yahoo! Mail, o único sem limite de espaço para > armazenamento! > http://br.mail.yahoo.com/ > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > >

Device links in Linux (starting in RedHat AS4 for example) are recreated at boot time *but* ownership and permissions return to default (root). To preserve the ownership and permission, you must configure the appropriate files under the /etc/udev/ structure. The /etc/rawdevices file stays the same if you are using raw devices. Redhat info: http://www.redhat.com/magazine/002dec04/features/udev/ example for raw devices as partitions on /dev/sdb: amis1.root> pwd /etc/udev/rules.d amis1.root> ls -l total 28 -rw-r--r-- 1 root root 3567 May 22 2006 50-udev.rules -rw-r--r-- 1 root root 507 May 22 2006 51-by-id.rules -rw-r--r-- 1 root root 409 May 1 2007 60-raw.rules -rw-r--r-- 1 root root 324 Jun 27 2006 90-ib.rules amis1.root> amis1.root> cat 60-raw* ACTION=="add", KERNEL=="sdb5", RUN+="/usr/bin/raw /dev/raw/raw1 %N" ACTION=="add", KERNEL=="sdb6", RUN+="/usr/bin/raw /dev/raw/raw2 %N" ACTION=="add", KERNEL=="sdb7", RUN+="/usr/bin/raw /dev/raw/raw3 %N" ACTION=="add", KERNEL=="sdb8", RUN+="/usr/bin/raw /dev/raw/raw4 %N" ACTION=="add", KERNEL=="sdb9", RUN+="/usr/bin/raw /dev/raw/raw5 %N" ACTION=="add", KERNEL=="sdb10", RUN+="/usr/bin/raw /dev/raw/raw6 %N" amis1.root> Bob Roussey Unix / Informix Administration Spirit Airlines Robert.Roussey@SpiritAir.com -----Original Message----- From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of Art S. Kagel (Oninit LLC) Sent: Wednesday, December 12, 2007 9:33 AM To: ids@iiug.org Subject: Re: Res: RE: Extent DB [10724] Cesar Inacio Martins wrote: > About Links on the manual: > > http://publib.boulder.ibm.com/infocenter/idshelp/v111/index.jsp?topic=/com.ibm.a dmin.doc/admin355.htm > Your example this is not a good idea, because the /dev will be recreate after > a reboot on your machine, and probably will lost the link /dev/sdb: > ln -s /usr/informix/rawdbspace /dev/sdb > Ceasar, Symbolic links (see the -s option to ln above) will survive if the file/directory/device they point to is removed from the system or, as in the case of device files on some systems, recreated at boot time. Even hard links will survive deletion of other links, it's just that after the recreation the new entry may point to different resources than the new object. Not a problem for soft or symbolic links as they are just a small file containing the real path. Since the OS has no easy/cheap way to track down what symlinks are pointing to a given object, it doesn't try. Once the path has been recreated the link will work fine. Art S. Kagel > The right thing to do, is create the link in a directory: > ln -s /usr/informix/rawdbspace /ifmx_data/chunk_xyz. > > _______________________________________ > Existem 10 tipos de pessoas no mundo, aqueles que compreendem binário e > aqueles que não > > ----- Mensagem original ---- > De: MICHAEL MEIER <freudi_t@yahoo.de> > Para: ids@iiug.org > Enviadas: Quarta-feira, 12 de Dezembro de 2007 7:58:30 > Assunto: Re: RE: Extent DB [10708] > > Wow. Links. Thats another hint. > So what I did is creating a dbspace /dev/sdb. > But I should > ln -s /usr/informix/rawdbspace /dev/sdb > and then use rawdbspace as chunk. And than I can replace or add a > diefferent > harddisk. Thats a nice hint. > All this is not in the books or somehow hidden !! Believe me, I read a > lot > before I decided to post here. > A last :-) question to that ln point. If I replace /dev/sdb with larger > > harddisk. Can I also resize, better increase, the dbspace. Or should I > build a > new chunk ? > > Freudi > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > Abra sua conta no Yahoo! Mail, o único sem limite de espaço para > armazenamento! > http://br.mail.yahoo.com/ > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > ******************************************************************************* Forum Note: Use "Reply" to post a response in the discussion forum.

If the device /dev/sdb still there after reboot, the will overwritten the link by /dev/sdb node, right? _______________________________________ Existem 10 tipos de pessoas no mundo, aqueles que compreendem binário e aqueles que não ----- Mensagem original ---- De: Art S. Kagel (Oninit LLC) <art@oninit.com> Para: ids@iiug.org Enviadas: Quarta-feira, 12 de Dezembro de 2007 14:32:43 Assunto: Re: Res: RE: Extent DB [10724] Cesar Inacio Martins wrote: > About Links on the manual: > > http://publib.boulder.ibm.com/infocenter/idshelp/v111/index.jsp?topic=/com.ibm.a dmin.doc/admin355.htm > Your example this is not a good idea, because the /dev will be recreate after > a reboot on your machine, and probably will lost the link /dev/sdb: > ln -s /usr/informix/rawdbspace /dev/sdb > Ceasar, Symbolic links (see the -s option to ln above) will survive if the file/directory/device they point to is removed from the system or, as in the case of device files on some systems, recreated at boot time. Even hard links will survive deletion of other links, it's just that after the recreation the new entry may point to different resources than the new object. Not a problem for soft or symbolic links as they are just a small file containing the real path. Since the OS has no easy/cheap way to track down what symlinks are pointing to a given object, it doesn't try. Once the path has been recreated the link will work fine. Art S. Kagel > The right thing to do, is create the link in a directory: > ln -s /usr/informix/rawdbspace /ifmx_data/chunk_xyz. > > _______________________________________ > Existem 10 tipos de pessoas no mundo, aqueles que compreendem binário e > aqueles que não > > ----- Mensagem original ---- > De: MICHAEL MEIER <freudi_t@yahoo.de> > Para: ids@iiug.org > Enviadas: Quarta-feira, 12 de Dezembro de 2007 7:58:30 > Assunto: Re: RE: Extent DB [10708] > > Wow. Links. Thats another hint. > So what I did is creating a dbspace /dev/sdb. > But I should > ln -s /usr/informix/rawdbspace /dev/sdb > and then use rawdbspace as chunk. And than I can replace or add a > diefferent > harddisk. Thats a nice hint. > All this is not in the books or somehow hidden !! Believe me, I read a > lot > before I decided to post here. > A last :-) question to that ln point. If I replace /dev/sdb with larger > > harddisk. Can I also resize, better increase, the dbspace. Or should I > build a > new chunk ? > > Freudi > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > Abra sua conta no Yahoo! Mail, o único sem limite de espaço para > armazenamento! > http://br.mail.yahoo.com/ > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > ******************************************************************************* Forum Note: Use "Reply" to post a response in the discussion forum. Abra sua conta no Yahoo! Mail, o único sem limite de espaço para armazenamento! http://br.mail.yahoo.com/

sorry... I am a little slow today.. if is possible create a link /dev/sdb obvious the device is not there... but the link will be overwritten only if this device appear after a reboot... _______________________________________ Existem 10 tipos de pessoas no mundo, aqueles que compreendem binário e aqueles que não ----- Mensagem original ---- De: Cesar Inacio Martins <cesar_inacio_martins@yahoo.com.br> Para: ids@iiug.org Enviadas: Quarta-feira, 12 de Dezembro de 2007 15:52:17 Assunto: Res: Res: RE: Extent DB [10728] If the device /dev/sdb still there after reboot, the will overwritten the link by /dev/sdb node, right? _______________________________________ Existem 10 tipos de pessoas no mundo, aqueles que compreendem binário e aqueles que não ----- Mensagem original ---- De: Art S. Kagel (Oninit LLC) <art@oninit.com> Para: ids@iiug.org Enviadas: Quarta-feira, 12 de Dezembro de 2007 14:32:43 Assunto: Re: Res: RE: Extent DB [10724] Cesar Inacio Martins wrote: > About Links on the manual: > > http://publib.boulder.ibm.com/infocenter/idshelp/v111/index.jsp?topic=/com.ibm.a dmin.doc/admin355.htm > Your example this is not a good idea, because the /dev will be recreate after > a reboot on your machine, and probably will lost the link /dev/sdb: > ln -s /usr/informix/rawdbspace /dev/sdb > Ceasar, Symbolic links (see the -s option to ln above) will survive if the file/directory/device they point to is removed from the system or, as in the case of device files on some systems, recreated at boot time. Even hard links will survive deletion of other links, it's just that after the recreation the new entry may point to different resources than the new object. Not a problem for soft or symbolic links as they are just a small file containing the real path. Since the OS has no easy/cheap way to track down what symlinks are pointing to a given object, it doesn't try. Once the path has been recreated the link will work fine. Art S. Kagel > The right thing to do, is create the link in a directory: > ln -s /usr/informix/rawdbspace /ifmx_data/chunk_xyz. > > _______________________________________ > Existem 10 tipos de pessoas no mundo, aqueles que compreendem binário e > aqueles que não > > ----- Mensagem original ---- > De: MICHAEL MEIER <freudi_t@yahoo.de> > Para: ids@iiug.org > Enviadas: Quarta-feira, 12 de Dezembro de 2007 7:58:30 > Assunto: Re: RE: Extent DB [10708] > > Wow. Links. Thats another hint. > So what I did is creating a dbspace /dev/sdb. > But I should > ln -s /usr/informix/rawdbspace /dev/sdb > and then use rawdbspace as chunk. And than I can replace or add a > diefferent > harddisk. Thats a nice hint. > All this is not in the books or somehow hidden !! Believe me, I read a > lot > before I decided to post here. > A last :-) question to that ln point. If I replace /dev/sdb with larger > > harddisk. Can I also resize, better increase, the dbspace. Or should I > build a > new chunk ? > > Freudi > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > Abra sua conta no Yahoo! Mail, o único sem limite de espaço para > armazenamento! > http://br.mail.yahoo.com/ > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > ******************************************************************************* Forum Note: Use "Reply" to post a response in the discussion forum. Abra sua conta no Yahoo! Mail, o único sem limite de espaço para armazenamento! http://br.mail.yahoo.com/ ******************************************************************************* Forum Note: Use "Reply" to post a response in the discussion forum. Abra sua conta no Yahoo! Mail, o único sem limite de espaço para armazenamento! http://br.mail.yahoo.com/

Cesar Inacio Martins wrote: OH! I was reading th OPs ln command wrong. Yes, if the /dev/sdb device really exists then a reboot will overwrite the original link to the file /usr/informix/rawdbspace. Unless he meant: ln -s /dev/sdb /usr/informix/rawdbspace Creating a link in /usr/informix named rawdbspace to the /dev/sdb device. Which is what I thought I was reading. That would be safe after a boot. Art S. Kagel > If the device /dev/sdb still there after reboot, the will overwritten the link > by /dev/sdb node, right? > > _______________________________________ > Existem 10 tipos de pessoas no mundo, aqueles que compreendem binário e > aqueles que não > > ----- Mensagem original ---- > De: Art S. Kagel (Oninit LLC) <art@oninit.com> > Para: ids@iiug.org > Enviadas: Quarta-feira, 12 de Dezembro de 2007 14:32:43 > Assunto: Re: Res: RE: Extent DB [10724] > > Cesar Inacio Martins wrote: > >> About Links on the manual: >> >> >> > > http://publib.boulder.ibm.com/infocenter/idshelp/v111/index.jsp?topic=/com.ibm.a dmin.doc/admin355.htm > >> Your example this is not a good idea, because the /dev will be >> > recreate > after > >> a reboot on your machine, and probably will lost the link /dev/sdb: >> ln -s /usr/informix/rawdbspace /dev/sdb >> >> > > Ceasar, > > Symbolic links (see the -s option to ln above) will survive if the > file/directory/device they point to is removed from the system or, as > in > the case of device files on some systems, recreated at boot time. Even > hard links will survive deletion of other links, it's just that after > the recreation the new entry may point to different resources than the > new object. Not a problem for soft or symbolic links as they are just a > > small file containing the real path. Since the OS has no easy/cheap way > > to track down what symlinks are pointing to a given object, it doesn't > try. Once the path has been recreated the link will work fine. > > Art S. Kagel > > >> The right thing to do, is create the link in a directory: >> ln -s /usr/informix/rawdbspace /ifmx_data/chunk_xyz. >> >> _______________________________________ >> Existem 10 tipos de pessoas no mundo, aqueles que compreendem >> > binário e > >> aqueles que não >> >> ----- Mensagem original ---- >> De: MICHAEL MEIER <freudi_t@yahoo.de> >> Para: ids@iiug.org >> Enviadas: Quarta-feira, 12 de Dezembro de 2007 7:58:30 >> Assunto: Re: RE: Extent DB [10708] >> >> Wow. Links. Thats another hint. >> So what I did is creating a dbspace /dev/sdb. >> But I should >> ln -s /usr/informix/rawdbspace /dev/sdb >> and then use rawdbspace as chunk. And than I can replace or add a >> diefferent >> harddisk. Thats a nice hint. >> All this is not in the books or somehow hidden !! Believe me, I read >> > a > >> lot >> before I decided to post here. >> A last :-) question to that ln point. If I replace /dev/sdb with >> > larger > >> harddisk. Can I also resize, better increase, the dbspace. Or should >> > I > >> build a >> new chunk ? >> >> Freudi >> >> >> >> > > ******************************************************************************* > >> Forum Note: Use "Reply" to post a response in the discussion forum. >> >> Abra sua conta no Yahoo! Mail, o único sem limite de espaço para >> armazenamento! >> http://br.mail.yahoo.com/ >> >> >> >> > > ******************************************************************************* > >> Forum Note: Use "Reply" to post a response in the discussion forum. >> >> >> > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > Abra sua conta no Yahoo! Mail, o único sem limite de espaço para > armazenamento! > http://br.mail.yahoo.com/ > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > >