iscsi-init-users Mailing List for Linux iSCSI boot initialization program
Brought to you by:
ifeoktistov
Menu
▾
▴
iscsi-init-users — Issues, announcements and discussions regarding iSCSI-init module
You can subscribe to this list here.
| 2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(18) |
Sep
(5) |
Oct
(7) |
Nov
(3) |
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2005 |
Jan
(1) |
Feb
|
Mar
(1) |
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2006 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
| 2007 |
Jan
(1) |
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
(1) |
Jul
|
Aug
(2) |
Sep
|
Oct
(3) |
Nov
|
Dec
|
| 2008 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(2) |
Sep
(2) |
Oct
(1) |
Nov
(3) |
Dec
(2) |
| 2009 |
Jan
(1) |
Feb
|
Mar
(1) |
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
| 2012 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2013 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(2) |
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
| 2014 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
| 2015 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2016 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
|
From: <pra...@gm...> - 2016-10-05 07:20:35
|
Hi Iscsi-init.sourceforge.net, My name isJames, I'm a Search Specialist and was doing research for another client when I came across your site. I wanted to share a few major issues I discovered that are currently harming your website search rankings: • Your website has multiple undesirable technical errors such as HTML errors, missing image alt tags etc. Confirm this by searching your Iscsi-init.sourceforge.net or website • The number of high quality and/or authoritative links pointing to your site is extremely low. • Active and regular updates and posts on social media portals to increase the popularity and brand awareness. We can help you fix these issues and get your website ranking on the 1st page of Google! Let me know if you are interested and I'll send you a proposal with our prices, SEO strategy for Iscsi-init.sourceforge.net, and results we have achieved for other clients. Sounds interesting? Feel free to ask questions or you can provide your phone number for me to call you. Kind Regards, James Search Specialist |
|
From: LucaDomenella <luc...@gm...> - 2012-02-02 15:31:56
|
Hi all, first of all let me tell you what's my goal: use xenserver 6 (citrix) booting from iSCSI SAN (Netapp). the server is a DELL poweregde with broadcom onboard NICs (eth0,1) and 2 Intel 82571EB (dual ports) (eth2,3,4,5). the eth0 is connected to a VLAN for management purposes, then i configured initiator and target on NIC in slot1 (eth2,3) on network1 and network2 (for multipathing, the storage is directly connected there). i'm trying to boot xen using iBFT, after many searches i've been able to boot from the sotrage directly and even using multipathing (its not documented for xenserver - if you need details, feel free to ask by email) the problem is i'm not able to use from xen anymore such nics to connect SRs (addictional disks from a storage not netapp, or another target) so the question is: when booting in iscsi using iBFT, can i use such NICs to connect other targets or are exclusively used by the target configured in the intel NIC ? or i did something wrong at configuration level ? i will try some tests with centos 6.2 later to see if i can use such nics or not, maybe its only a xen server problem. please i dont find details about that best regards, Luca |
|
From: 【 キャッシング情報 】 <ge...@ni...> - 2008-09-17 13:19:49
|
---------------≪おまとめローン 800万円迄ご融資≫-------------- 【３０日間お利息無料】新規ご契約キャンペーン http://alpha.cash-x.net/ □□□□□ 用途に合わせた３つのコース □□□□□ 即日融資のクイックローン 大型ご融資の多目的ローン 用途はご自由 とにかく支払いを１つにまとめたい方へのおまとめローン □□□□□□□□□□□□□□□□□□□□□□□□□□□ □・┓□・┓□・┓□・┓□・□■・┓■・┓■・┓■・┓ ８月は特別融資強化月間につき金利も低金利優遇！ ┗・■┗・■┗・■┗・■□・□┗・□┗・□┗・□┗・□ http://alpha.cash-x.net/ ＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿ ￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣ ┏─・─・─・─・─・─・─・─・─・─・─・─・─・─・─┓ 全国の提携銀行・コンビにATMで借入・ご返済 ⇒残高紹介・振込み予約がモバイルから出来ます ┗・─・─・─・─・─・─・─・─・─・─・─・─・─・─・┛ http://alpha.cash-x.net/ ￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣ ■おまとめローン ８００万円迄！ ■クイックローン １００万円迄即日ご融資 ■多目的ローン ５００万円迄の用途は自由 ▼このチャンスに是非▼ http://alpha.cash-x.net/ ＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿ ￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣ ------------------------------------------------------------------ 審査の結果によっては、ご入会をお断りさせていただく場合も ございますので、予めご了承ください。 既にお申込みをされたお客様へ配信の節は、重ねてのご案内を ご容赦ください。 ------------------------------------------------------------------ …━━ 最後までお読みいただきありがとうございました ━━━… アルファクレジット株式会社 ■ご利用可能枠/10万円〜８００万円 ■ご融資利率/実質年率 2.5％〜 ＊金融情勢等の変化によりご融資利率を変更させていただく場合も ございます。 ＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿ ￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣ |
|
From: 【 キャッシング情報 】 <ge...@ni...> - 2008-09-06 20:49:31
|
---------------≪おまとめローン 800万円迄ご融資≫-------------- 【３０日間お利息無料】新規ご契約キャンペーン http://urban.loan-jp.net/ □□□□□ 用途に合わせた３つのコース □□□□□ 即日融資のクイックローン 大型ご融資の多目的ローン 用途はご自由 とにかく支払いを１つにまとめたい方へのおまとめローン □□□□□□□□□□□□□□□□□□□□□□□□□□□ □・┓□・┓□・┓□・┓□・□■・┓■・┓■・┓■・┓ ８月は特別融資強化月間につき金利も低金利優遇！ ┗・■┗・■┗・■┗・■□・□┗・□┗・□┗・□┗・□ http://urban.loan-jp.net/ ＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿ ￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣ ┏─・─・─・─・─・─・─・─・─・─・─・─・─・─・─┓ 全国の提携銀行・コンビにATMで借入・ご返済 ⇒残高紹介・振込み予約がモバイルから出来ます ┗・─・─・─・─・─・─・─・─・─・─・─・─・─・─・┛ http://urban.loan-jp.net/ ￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣ ■おまとめローン ８００万円迄！ ■クイックローン １００万円迄即日ご融資 ■多目的ローン ５００万円迄の用途は自由 ▼このチャンスに是非▼ http://urban.loan-jp.net/ ＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿ ￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣ ------------------------------------------------------------------ 審査の結果によっては、ご入会をお断りさせていただく場合も ございますので、予めご了承ください。 既にお申込みをされたお客様へ配信の節は、重ねてのご案内を ご容赦ください。 ------------------------------------------------------------------ …━━ 最後までお読みいただきありがとうございました ━━━… 株式会社ア−バンクレジット ■ご利用可能枠/10万円〜８００万円 ■ご融資利率/実質年率 2.5％〜 ＊金融情勢等の変化によりご融資利率を変更させていただく場合も ございます。 ＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿ ￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣ |
|
From: 【 キャッシング情報 】 <ge...@ni...> - 2008-08-23 13:34:50
|
……………………………………………………………………………………………
◇◇・‥……………………………………………┐
期間限定 おまとめローン
└……………………………………………………◇◇
NICOSのおまとめローン
http://nicos.fgloan.net/
……………………………………………………………………………………………
┏━┳━┳━┳━┳━┳━┳━┳━┳━┳━┳━┳━┳━┳━┳━┳━┳━┓
ニコスの期間限定おまとめローン ２００８年１２月末日迄
┗━┻━┻━┻━┻━┻━┻━┻━┻━┻━┻━┻━┻━┻━┻━┻━┻━┛
◇◇今が最大のチャンス！！◇◇
最大８００万円までの おまとめローン
即日ご融資のONE DAY300も実施中
http://nicos.fgloan.net/
―――――――――――――――――――――――――――――――――――
◎ 期間限定の低い金利で対応中！！
―――――――――――――――――――――――――――――――――――
ONE DAY300 実質年率5.4%
おまとめローン800 実質年率9.5％
‥‥‥‥‥‥‥‥‥‥‥‥‥‥‥‥‥‥‥‥‥‥‥‥‥‥‥‥‥‥
┏━━━━━━━━━↓↓━ご利用はこちらから━↓↓━━━━━━━━━┓
http://nicos.fgloan.net/
┗━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛
━━━━━━ 最後までお読みいただきありがとうございました ━━━━━
＊審査の結果によってはご融資できない場合もございますので、
予めご了承下さいますようお願い申し上げます。
＊既にお申込をされたお客様へ配信の節は、重ねてのご案内をご容赦下さい。
───────────────────────────────────
◆ ニコスクレジット ◆
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
----------------------------------------------------------------
このメールは特定電子メール送信適正化法・改正特定商取引法を遵守の上
送信しておりますが、ご不要な方には大変ご迷惑をおかけいたしました。
■配信元 ファーストプレス
■所在地
東京都港区麻布十番1-18-3
■配信停止を希望される方はお手数ですが下記アドレスに。
配信停止： in...@fi...
---------------------------------------------------------------
|
|
From: 【 キャッシング情報 】 <ge...@ni...> - 2008-08-03 04:06:23
|
╋─┳─┳─┳─┳─┳─┳─┳─┳─┳─┳─╋ │事│業│者│向│・│ご│融│資│で│す│！│━━━━━━━━━━━…╋ ╋─┻─┻─┻─┻─┻─┻─┻─┻─┻─┳─╋ ★〓 無担保 最大２０００万円までご融資いたします。 〓★ 銀行・大手消費者金融の貸し渋りの今 貴方のセカンドバンク ※設立及び開業１年以上・月商５００万円以上の事業者の方 取引実績・今後の事業計画の将来性の認められる方ならあきらめないで ▼▼▼ 年利6.0〜13.5％の低金利で返済計画も余裕をもって ▼▼▼ http://global.loan-x.net/ ◆ グローバルコミニュケーション ◆ ▼▼▼ おまとめローン・事業資金・車の購入 用途は自由です。 ▼▼▼ http://global.loan-x.net/ ∞∞∞∞∞∞∞∞∞∞∞∞∞∞∞∞∞∞∞∞∞∞∞∞∞∞∞∞∞∞∞∞∞∞∞∞ ┏━┓┏━┓┏━┓┏━┓┏━┓┏━┓┏━┓┏━┓┏━┓┏━┓┏━┓ ■グローバルコミニュケーション の ご融資 各コースのご案内 ■ ┗━┛┗━┛┗━┛┗━┛┗━┛┗━┛┗━┛┗━┛┗━┛┗━┛┗━┛ ┏────────────────────────── ◇…即日ご融資１０００万円 ビジネスローン ┗────────────────────────── ┏────────────────────────── ◇…売掛債権で３０００万円迄ご融資 売掛債権担保融資 ┗────────────────────────── ┏────────────────────────── ◇…使用目的自由 ２０００万円迄対応 ビジネスサポートローン ┗────────────────────────── ┏────────────────────────── ◇…入会金・年会費は永久無料！ ┗────────────────────────── ∞∞∞∞∞∞∞∞∞∞∞∞∞∞∞∞∞∞∞∞∞∞∞∞∞∞∞∞∞∞∞∞∞∞∞∞ ▼▼▼ 事業者のセカンドバンクに絶対の自信 あきらめないで今すぐ ▼▼▼ http://global.loan-x.net/ ━━━━━━ 最後までお読みいただきありがとうございました ━━━━━ ＊審査の結果によってはご融資できない場合もございますので、 予めご了承下さいますようお願い申し上げます。 ＊既にお申込をされたお客様へ配信の節は、重ねてのご案内をご容赦下さい。 ─────────────────────────────────── ◆ グローバルコミニュケーション ◆ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ ---------------------------------------------------------------- このメールは特定電子メール送信適正化法・改正特定商取引法を遵守の上 送信しておりますが、ご不要な方には大変ご迷惑をおかけいたしました。 ■配信元 Fory Stone ■所在地 東京都港区高輪1-2-4 ■配信停止を希望される方はお手数ですが下記アドレスに。 配信停止： in...@fo... --------------------------------------------------------------- |
☆:;;::;;:*:;;::;;:*:;;::;;:*:;;::;;:*:;;::;;:☆ isc...@li... 様 （今回のみの配信となります） １０月最新・特別リニューアル号！！ ◇公式サイト【現金自動集金機/NEW設計図'07】高額収集システム◆ ●数千円から数万円程度の入金が毎日の様に発生します 詳しくは公式HPまで(o^-’)b☆彡（※新リニューアル開始！！） http://it-nikoru.hp.infoseek.co.jp/ あなたの常識が変わる！！ ●文字通り「現金」を「自動的」に稼ぐ副収入システムです ●設置後は特に何もしなくて平気です （週に一回、10分程度のメンテナンスが必要） ●パソコンの難しい知識は必要ありません。初心者でもOKです。 http://it-nikoru.hp.infoseek.co.jp/ by_ニコルIT開発システム'０７ 管理者名：野田准一 連絡先：pc_...@ya... ＵＲＬ：http://it-nikoru.hp.infoseek.co.jp -PC NIKORU OFFICIAL WEB SITE- Copyright (C) 2007 International System, All rights reserved. ☆:;;::;;:*:;;::;;:*:;;::;;:*:;;::;;:*:;;::;;:☆ （このメールは、PC NIKORU OFFICIAL WEB SITEから 無料サービス配信されたメールマガジンです。） ※今回のみの配信となりますが、 ごく稀に重複してメールが配信されてしまう事もありますので、 今後の配信停止をご希望される場合は、 お手数ですが下記をクリックして下さいませ。 http://www.geocities.jp/sayasaya_netnet/newpage1.html ※「このアドレスは登録されていません」 とメッセージが出る事がありますが、 その場合はすでに配信停止が完了しておりますのでご安心下さいませ。 もしそれでも万が一配信が止まらない場合や御心配な場合は こちらpc_...@ya...まで 「購読解除」という件名で空メール送信して下さいませ。 手動で配信解除の処理を致します。 ☆:;;::;;:*:;;::;;:*:;;::;;:*:;;::;;:*:;;::;;:☆ |
|
From: <cr...@c-...> - 2007-10-07 19:58:23
|
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 【 好評おまとめローン９００ 只今 実施中！！ 】 【 お申込から融資実行までとにかく速い 】 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ ▼ オリエンタルエクスプレス ▼ http://www.safe-ray.info/ --------------------------------------------------------------- ┏━┓┏━┓┏━┓┏━┓ ●まずはご融資自動診断 ┃自┃┃動┃┃診┃┃断┃ ●ご融資可能額をメールでお知らせ ┗━┛┗━┛┗━┛┗━┛ ●診断額は即日ご融資 --------------------------------------------------------------- http://www.safe-ray.info/ ■オリエンタルエクスプレスなら■ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ ◆100万円ご融資実行時間 平均35分！！ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ ◆300万円ご融資実行時間 平均45分！！ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ ◆500万円ご融資実行時間 平均65分！！ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ ◆900万円ご融資実行時間 平均80分！！ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ http://www.safe-ray.info/ ---------------------------------------------------------------- このメールは特定電子メール送信適正化法・改正特定商取引法を遵守の上 送信しておりますが、ご不要な方には大変ご迷惑をおかけいたしました。 ■配信元 トライアルフリー ■所在地 東京都港区六本木5-3-8 ■配信停止を希望される方はお手数ですが下記アドレスに。 配信停止： in...@tf... ---------------------------------------------------------------- |
|
From:
<pc_...@ya...> - 2007-10-01 20:33:21
|
☆:;;::;;:*:;;::;;:*:;;::;;:*:;;::;;:*:;;::;;:☆ isc...@li... 様 （今回のみの配信となります） １０月最新リニューアル号！！ ◇公式サイト【現金自動集金機/NEW設計図'07】高額収集システム◆ ●数千円から数万円程度の入金が毎日の様に発生します 詳しくは公式HPまで(o^-’)b☆彡 （※新リニューアル開始！！） http://it-nikoru.hp.infoseek.co.jp/ あなたの常識が変わる！！ ●文字通り「現金」を「自動的」に稼ぐ副収入システムです ●設置後は特に何もしなくて平気です （週に一回、10分程度のメンテナンスが必要） ●パソコンの難しい知識は必要ありません。初心者でもOKです。 http://it-nikoru.hp.infoseek.co.jp/ by_ニコルIT開発システム'０７ 管理者名：野田准一 連絡先：pc_...@ya... ＵＲＬ：http://it-nikoru.hp.infoseek.co.jp -PC NIKORU OFFICIAL WEB SITE- Copyright (C) 2007 International System, All rights reserved. ☆:;;::;;:*:;;::;;:*:;;::;;:*:;;::;;:*:;;::;;:☆ （このメールは、PC NIKORU OFFICIAL WEB SITEから 無料サービス配信されたメールマガジンです。） ※今回のみの配信となりますが、 ごく稀に重複してメールが配信されてしまう事もありますので、 万が一配信が止まらない場合や御心配な場合はお手数ですが こちらpc_...@ya...まで 「購読解除」という件名で空メール送信して下さいませ。 手動で配信解除の処理を致します。 ☆:;;::;;:*:;;::;;:*:;;::;;:*:;;::;;:*:;;::;;:☆ |
〓〓〓〓〓〓〓〓〓〓〓〓〓〓〓〓〓〓〓〓〓〓〓〓〓〓〓〓〓〓〓
〜〜 STARおまとめローン 新登場！！ 無担保1000万 〜〜
〓〓〓〓〓〓〓〓〓〓〓〓〓〓〓〓〓〓〓〓〓〓〓〓〓〓〓〓〓〓〓
http://www.filspeed.info/
――― 24時間オペレーター対応 ―――『本当に急なご融資すぐ対応 』
■╋■━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
╋■┛【 まずはご融資自動診断 】・・安心の低金利 2.5％〜11.5％♪
■┛━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
――― 24時間オペレーター対応 ―――『本当に急なご融資すぐ対応 』
http://www.filspeed.info/
■STARクレジットの各コース■
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
◆他社おまとめローンに＋アルファーでご融資。
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
----------------------------------------------------
最大1000万円までのご融資を準備しております。
----------------------------------------------------
http://www.filspeed.info/
■即日300万円までご融資対応■
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
◆急なご利用でも即日口座にお振込み。
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
▼お申し込みから15分で対応できます。
----------------------------------------------------
後日カードが届きますのでATMでご返済。
----------------------------------------------------
http://www.filspeed.info/
■実質年率を大幅に引き下げ■
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
◆大口VIPローンなら2.5%の金利で1000万円まで対応。
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
http://www.filspeed.info/
----------------------------------------------------------------
このメールは特定電子メール送信適正化法・改正特定商取引法を遵守の上
送信しておりますが、ご不要な方には大変ご迷惑をおかけいたしました。
■配信元 DIMPLE LIFE
■所在地
東京都新宿区東新宿3-1-3
■配信停止を希望される方はお手数ですが下記アドレスに。
配信停止： dim...@ya...
----------------------------------------------------------------
|
|
From: Christian J. <chr...@je...> - 2007-06-06 18:08:41
|
|
From: <de...@ya...> - 2007-04-20 20:44:01
|
はじめまして美樹です。 掲示板で見て趣味合うかなって思ってメールしちゃいました。 イキナリでゴメンなさいm(__)m こういう感じで知り合えるのに憧れてて初挑戦しちゃいました。 お返事もらえたら簡単な自己紹介しますネ(^_-)-☆ もしそんな気なかったらそう言ってもらえれば諦めますので。 もちろん仲良くなれた方が嬉しいけど。 お返事気長に待ってま〜す(^_^)/~ http://www.star-lightz.com/m-box |
|
From: Rafael H. <rhi...@ha...> - 2007-01-22 18:35:17
|
I have 2 systems, a Dell 1950 (x86_64) and a Dell 1750 (x86): [root@var1 iscsi-init-4.0.1.11]# uname -a Linux var1.haverford.edu 2.6.9-42.0.3.ELsmp #1 SMP Mon Sep 25 17:24:31 EDT 2006 x86_64 x86_64 x86_64 GNU/Linux [root@var2 iscsi-init-4.0.1.11]# uname -a Linux var2 2.6.9-42.0.3.ELsmp #1 SMP Mon Sep 25 17:28:02 EDT 2006 i686 i686 i386 GNU/Linux Both system are running an up2date RedHat EL 4 (Update 4) system. [root@var1 iscsi-init-4.0.1.11]# cat /etc/redhat-release Red Hat Enterprise Linux AS release 4 (Nahant Update 4) [root@var2 iscsi-init-4.0.1.11]# cat /etc/redhat-release Red Hat Enterprise Linux AS release 4 (Nahant Update 4) Both systems have the needed kernel-devel package and updated gcc... Running make on the non-x86_64 system works w/o any problems. [root@var2 ~]# tar xzf iscsi-init-4.0.1.11.tar.gz [root@var2 ~]# cd iscsi-init-4.0.1.11 [root@var2 iscsi-init-4.0.1.11]# ls ChangeLog dhcpd.conf.SAMPLE iscsi.conf.SAMPLE iscsi-init.h Makefile COPYING init.SAMPLE.Fedora iscsi_init.c linuxrc.SAMPLE.SuSE README [root@var2 iscsi-init-4.0.1.11]# make make -C /lib/modules/2.6.9-42.0.3.ELsmp/build SUBDIRS=/root/iscsi-init-4.0.1.11 modules make[1]: Entering directory `/usr/src/kernels/2.6.9-42.0.3.EL-smp-i686' CC [M] /root/iscsi-init-4.0.1.11/iscsi_init.o Building modules, stage 2. MODPOST CC /root/iscsi-init-4.0.1.11/iscsi_init.mod.o LD [M] /root/iscsi-init-4.0.1.11/iscsi_init.ko make[1]: Leaving directory `/usr/src/kernels/2.6.9-42.0.3.EL-smp-i686' [root@var2 iscsi-init-4.0.1.11]# ls -l total 564 -rw-r--r-- 1 nfsnobody nfsnobody 858 Jan 27 2005 ChangeLog -rw-r--r-- 1 nfsnobody nfsnobody 18009 Jul 13 2001 COPYING -rw-r--r-- 1 nfsnobody nfsnobody 675 Sep 30 2004 dhcpd.conf.SAMPLE -rwxr-xr-x 1 root root 1341 Jan 27 2005 init.SAMPLE.Fedora -rw-r--r-- 1 nfsnobody nfsnobody 4473 Mar 27 2004 iscsi.conf.SAMPLE -rw-r--r-- 1 nfsnobody nfsnobody 39748 Jan 27 2005 iscsi_init.c -rw-r--r-- 1 nfsnobody nfsnobody 4596 Jan 27 2005 iscsi-init.h -rw-r--r-- 1 root root 227041 Jan 22 14:25 iscsi_init.ko -rw-r--r-- 1 root root 2157 Jan 22 14:25 iscsi_init.mod.c -rw-r--r-- 1 root root 40116 Jan 22 14:25 iscsi_init.mod.o -rw-r--r-- 1 root root 187884 Jan 22 14:25 iscsi_init.o -rwxr-xr-x 1 nfsnobody nfsnobody 916 Jan 27 2005 linuxrc.SAMPLE.SuSE -rw-r--r-- 1 nfsnobody nfsnobody 178 Nov 24 2004 Makefile -rw-r--r-- 1 nfsnobody nfsnobody 6672 Jan 27 2005 README [root@var2 iscsi-init-4.0.1.11]# Running make on the x86_64 system yields the following errors... [root@var1 ~]# tar xzf iscsi-init-4.0.1.11.tar.gz [root@var1 ~]# cd iscsi-init-4.0.1.11 [root@var1 iscsi-init-4.0.1.11]# ls ChangeLog dhcpd.conf.SAMPLE iscsi.conf.SAMPLE iscsi-init.h Makefile COPYING init.SAMPLE.Fedora iscsi_init.c linuxrc.SAMPLE.SuSE README [root@var1 iscsi-init-4.0.1.11]# make make -C /lib/modules/2.6.9-42.0.3.ELsmp/build SUBDIRS=/root/iscsi-init-4.0.1.11 modules make[1]: Entering directory `/usr/src/kernels/2.6.9-42.0.3.EL-smp-x86_64' CC [M] /root/iscsi-init-4.0.1.11/iscsi_init.o /root/iscsi-init-4.0.1.11/iscsi_init.c:98: error: syntax error before "unlink" /root/iscsi-init-4.0.1.11/iscsi_init.c:98: warning: type defaults to `int' in declaration of `_syscall1' /root/iscsi-init-4.0.1.11/iscsi_init.c:98: warning: function declaration isn't a prototype /root/iscsi-init-4.0.1.11/iscsi_init.c:99: error: syntax error before "ioctl" /root/iscsi-init-4.0.1.11/iscsi_init.c:99: warning: type defaults to `int' in declaration of `_syscall3' /root/iscsi-init-4.0.1.11/iscsi_init.c:99: warning: function declaration isn't a prototype /root/iscsi-init-4.0.1.11/iscsi_init.c:100: error: syntax error before "mknod" /root/iscsi-init-4.0.1.11/iscsi_init.c:100: warning: type defaults to `int' in declaration of `_syscall3' /root/iscsi-init-4.0.1.11/iscsi_init.c:100: warning: function declaration isn't a prototype /root/iscsi-init-4.0.1.11/iscsi_init.c:102: error: syntax error before "open" /root/iscsi-init-4.0.1.11/iscsi_init.c:102: warning: type defaults to `int' in declaration of `_syscall3' /root/iscsi-init-4.0.1.11/iscsi_init.c:102: warning: function declaration isn't a prototype /root/iscsi-init-4.0.1.11/iscsi_init.c:103: error: syntax error before "close" /root/iscsi-init-4.0.1.11/iscsi_init.c:103: warning: type defaults to `int' in declaration of `_syscall1' /root/iscsi-init-4.0.1.11/iscsi_init.c:103: warning: function declaration isn't a prototype /root/iscsi-init-4.0.1.11/iscsi_init.c:104: error: syntax error before "read" /root/iscsi-init-4.0.1.11/iscsi_init.c:104: warning: type defaults to `int' in declaration of `_syscall3' /root/iscsi-init-4.0.1.11/iscsi_init.c:104: warning: function declaration isn't a prototype /root/iscsi-init-4.0.1.11/iscsi_init.c: In function `open_ctl_dev': /root/iscsi-init-4.0.1.11/iscsi_init.c:1021: warning: implicit declaration of function `mknod' /root/iscsi-init-4.0.1.11/iscsi_init.c: In function `ioctl_establish_session': /root/iscsi-init-4.0.1.11/iscsi_init.c:1167: warning: implicit declaration of function `ioctl' /root/iscsi-init-4.0.1.11/iscsi_init.c: At top level: /root/iscsi-init-4.0.1.11/iscsi_init.c:103: warning: '_syscall1' declared `static' but never defined /root/iscsi-init-4.0.1.11/iscsi_init.c:104: warning: '_syscall3' declared `static' but never defined make[2]: *** [/root/iscsi-init-4.0.1.11/iscsi_init.o] Error 1 make[1]: *** [_module_/root/iscsi-init-4.0.1.11] Error 2 make[1]: Leaving directory `/usr/src/kernels/2.6.9-42.0.3.EL-smp-x86_64' make: *** [default] Error 2 [root@var1 iscsi-init-4.0.1.11]# ls -l total 104 -rw-r--r-- 1 nfsnobody nfsnobody 858 Jan 27 2005 ChangeLog -rw-r--r-- 1 nfsnobody nfsnobody 18009 Jul 13 2001 COPYING -rw-r--r-- 1 nfsnobody nfsnobody 675 Sep 30 2004 dhcpd.conf.SAMPLE -rwxr-xr-x 1 root root 1341 Jan 27 2005 init.SAMPLE.Fedora -rw-r--r-- 1 nfsnobody nfsnobody 4473 Mar 27 2004 iscsi.conf.SAMPLE -rw-r--r-- 1 nfsnobody nfsnobody 39748 Jan 27 2005 iscsi_init.c -rw-r--r-- 1 nfsnobody nfsnobody 4596 Jan 27 2005 iscsi-init.h -rwxr-xr-x 1 nfsnobody nfsnobody 916 Jan 27 2005 linuxrc.SAMPLE.SuSE -rw-r--r-- 1 nfsnobody nfsnobody 178 Nov 24 2004 Makefile -rw-r--r-- 1 nfsnobody nfsnobody 6672 Jan 27 2005 README [root@var1 iscsi-init-4.0.1.11]# Any help or suggestions to get iscsi-init to make on a x86_64 system would be greatly appreciated. Thanks, --Raf -- ========================================================================= Rafael A. Hinojosa ph# 610 896 1312 Technical Support Analyst fax# 610 896 1429 Networking & Systems e-mail: rhi...@ha... College Information Resources url: http://rhinojos.people.haverford.edu/ Haverford College |
|
From: Mike N. <mr....@gm...> - 2006-11-16 18:36:30
|
Hi! I'm trying to comple iscsi-init-4.0.3 on : Linux zombywoof 2.6.17-1.2142_FC4smp #1 SMP Tue Jul 11 22:59:20 EDT 2006 x86_64 x86_64 x86_64 GNU/Linux I get compile errors as shown below. Has anyone been able to get this to compile and work? Thanks. Regards, Mike [miken@zombywoof iscsi-init-4.0.3]$ make make -C /lib/modules/2.6.17-1.2142_FC4smp/build SUBDIRS=/home/miken/iSCSI-Boot/iscsi-init-4.0.3 modules make[1]: Entering directory `/usr/src/kernels/2.6.17-1.2142_FC4-smp-x86_64' CC [M] /home/miken/iSCSI-Boot/iscsi-init-4.0.3/iscsi_init.o /home/miken/iSCSI-Boot/iscsi-init-4.0.3/iscsi_init.c:86: error: syntax error before 'unlink' /home/miken/iSCSI-Boot/iscsi-init-4.0.3/iscsi_init.c:86: warning: type defaults to 'int' in declaration of '_syscall1' /home/miken/iSCSI-Boot/iscsi-init-4.0.3/iscsi_init.c:86: warning: function declaration isn't a prototype /home/miken/iSCSI-Boot/iscsi-init-4.0.3/iscsi_init.c:87: error: syntax error before 'ioctl' /home/miken/iSCSI-Boot/iscsi-init-4.0.3/iscsi_init.c:87: warning: type defaults to 'int' in declaration of '_syscall3' /home/miken/iSCSI-Boot/iscsi-init-4.0.3/iscsi_init.c:87: warning: function declaration isn't a prototype /home/miken/iSCSI-Boot/iscsi-init-4.0.3/iscsi_init.c:88: error: syntax error before 'mknod' /home/miken/iSCSI-Boot/iscsi-init-4.0.3/iscsi_init.c:88: warning: type defaults to 'int' in declaration of '_syscall3' /home/miken/iSCSI-Boot/iscsi-init-4.0.3/iscsi_init.c:88: warning: function declaration isn't a prototype /home/miken/iSCSI-Boot/iscsi-init-4.0.3/iscsi_init.c:90: error: syntax error before 'open' /home/miken/iSCSI-Boot/iscsi-init-4.0.3/iscsi_init.c:90: warning: type defaults to 'int' in declaration of '_syscall3' /home/miken/iSCSI-Boot/iscsi-init-4.0.3/iscsi_init.c:90: warning: function declaration isn't a prototype /home/miken/iSCSI-Boot/iscsi-init-4.0.3/iscsi_init.c:91: error: syntax error before 'close' /home/miken/iSCSI-Boot/iscsi-init-4.0.3/iscsi_init.c:91: warning: type defaults to 'int' in declaration of '_syscall1' /home/miken/iSCSI-Boot/iscsi-init-4.0.3/iscsi_init.c:91: warning: function declaration isn't a prototype /home/miken/iSCSI-Boot/iscsi-init-4.0.3/iscsi_init.c:92: error: syntax error before 'read' /home/miken/iSCSI-Boot/iscsi-init-4.0.3/iscsi_init.c:92: warning: type defaults to 'int' in declaration of '_syscall3' /home/miken/iSCSI-Boot/iscsi-init-4.0.3/iscsi_init.c:92: warning: function declaration isn't a prototype /home/miken/iSCSI-Boot/iscsi-init-4.0.3/iscsi_init.c: In function 'iscsi_open_devs': /home/miken/iSCSI-Boot/iscsi-init-4.0.3/iscsi_init.c:101: error: implicit declaration of function 'rtnl_shlock' /home/miken/iSCSI-Boot/iscsi-init-4.0.3/iscsi_init.c:135: error: implicit declaration of function 'rtnl_shunlock' /home/miken/iSCSI-Boot/iscsi-init-4.0.3/iscsi_init.c: In function 'iscsi_dev_ioctl': /home/miken/iSCSI-Boot/iscsi-init-4.0.3/iscsi_init.c:176: error: implicit declaration of function 'devinet_ioctl' /home/miken/iSCSI-Boot/iscsi-init-4.0.3/iscsi_init.c: At top level: /home/miken/iSCSI-Boot/iscsi-init-4.0.3/iscsi_init.c:181: warning: 'struct rtentry' declared inside parameter list /home/miken/iSCSI-Boot/iscsi-init-4.0.3/iscsi_init.c:181: warning: its scope is only this definition or declaration, which is probably not what you want /home/miken/iSCSI-Boot/iscsi-init-4.0.3/iscsi_init.c: In function 'iscsi_route_ioctl': /home/miken/iSCSI-Boot/iscsi-init-4.0.3/iscsi_init.c:187: error: implicit declaration of function 'ip_rt_ioctl' /home/miken/iSCSI-Boot/iscsi-init-4.0.3/iscsi_init.c: In function 'iscsi_setup_routes': /home/miken/iSCSI-Boot/iscsi-init-4.0.3/iscsi_init.c:238: error: storage size of 'rm' isn't known /home/miken/iSCSI-Boot/iscsi-init-4.0.3/iscsi_init.c:250: error: 'RTF_UP' undeclared (first use in this function) /home/miken/iSCSI-Boot/iscsi-init-4.0.3/iscsi_init.c:250: error: (Each undeclared identifier is reported only once /home/miken/iSCSI-Boot/iscsi-init-4.0.3/iscsi_init.c:250: error: for each function it appears in.) /home/miken/iSCSI-Boot/iscsi-init-4.0.3/iscsi_init.c:250: error: 'RTF_GATEWAY' undeclared (first use in this function) /home/miken/iSCSI-Boot/iscsi-init-4.0.3/iscsi_init.c:255: error: 'RTF_HOST' undeclared (first use in this function) /home/miken/iSCSI-Boot/iscsi-init-4.0.3/iscsi_init.c:238: warning: unused variable 'rm' /home/miken/iSCSI-Boot/iscsi-init-4.0.3/iscsi_init.c: At top level: /home/miken/iSCSI-Boot/iscsi-init-4.0.3/iscsi_init.c:306: warning: initialization from incompatible pointer type /home/miken/iSCSI-Boot/iscsi-init-4.0.3/iscsi_init.c: In function 'iscsi_bootp_send_if': /home/miken/iSCSI-Boot/iscsi-init-4.0.3/iscsi_init.c:408: error: 'ARPHRD_IEEE802_TR' undeclared (first use in this function) /home/miken/iSCSI-Boot/iscsi-init-4.0.3/iscsi_init.c:409: error: 'ARPHRD_IEEE802' undeclared (first use in this function) /home/miken/iSCSI-Boot/iscsi-init-4.0.3/iscsi_init.c: In function 'open_ctl_dev': /home/miken/iSCSI-Boot/iscsi-init-4.0.3/iscsi_init.c:1060: error: implicit declaration of function 'mknod' /home/miken/iSCSI-Boot/iscsi-init-4.0.3/iscsi_init.c: In function 'ioctl_establish_session': /home/miken/iSCSI-Boot/iscsi-init-4.0.3/iscsi_init.c:1202: error: implicit declaration of function 'ioctl' make[2]: *** [/home/miken/iSCSI-Boot/iscsi-init-4.0.3/iscsi_init.o] Error 1 make[1]: *** [_module_/home/miken/iSCSI-Boot/iscsi-init-4.0.3] Error 2 make[1]: Leaving directory `/usr/src/kernels/2.6.17-1.2142_FC4-smp-x86_64' make: *** [default] Error 2 -- Regards, Mike Nielsen |
|
From: Igor F. <ife...@ya...> - 2005-04-09 23:52:17
|
This release is multipath ready. See README in the
package with short description how to make it work
with DM.
--
Changes in version 4.0.2.1:
- added support of ConnFailTimeout option in
iscsi.conf
This option needs for multipath via
device-mapper.
- now you can bind targets to the specific
interfaces
via interface prefix in target IP. See README
for
details. This will induce routing table setup
via
specified network interfaces for target IP's
which
don't belong to these interfaces subnets.
- improved syntax for targets with multple portal
groups
simplifies multipath configurations. Now you can
just
specify iscsi-target option like this:
"192.168.1.1,192.168.2.1:iqn.1992-08.com.netapp:sn.16804546"
or like this
"eth0:192.168.1.1,eth1:192.168.2.1:iqn.1992-08.com.netapp:sn.16804546"
The same syntax is valid for "root-path" via
DHCP.
__________________________________
Do you Yahoo!?
Make Yahoo! your home page
http://www.yahoo.com/r/hs
|
|
From: Igor F. <ife...@ya...> - 2005-03-20 18:45:46
|
iscsi-init-4.0.2 has been released.
Changes in version 4.0.2:
- this version works with linux-iscsi-4.0.2
- multiple targets can be specified in
iscsi-target kernel parameter or can
be retrived via DHCP "root-path" option. See
README for details.
- multiple interfaces can be specified in iscsi-if
parameter.
See README for details.
__________________________________
Do you Yahoo!?
Yahoo! Small Business - Try our new resources site!
http://smallbusiness.yahoo.com/resources/
|
|
From: Igor F. <ife...@ya...> - 2005-01-28 19:27:57
|
It works with linux-iscsi-4.0.1.11. The new feature it supports is you can specify multiple targets in iscsi-target kernel paarameter. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com |
|
From: Matt C. <ma...@cl...> - 2004-11-11 20:48:27
|
Hi All, I was am trying to get the 3.4.2.3 module to compile under linux 2.4.21, and I get the following errors: gcc -O2 -Wall -Wstrict-prototypes -fno-strict-aliasing -DMODULE -D__KERNEL__ -DMODVERSIONS -c iscsi_init.c -I/usr/src/linux-2.4.21/include iscsi_init.c: In function `ioctl_establish_session': iscsi_init.c:1129: parse error before `*' iscsi_init.c:1130: `word' undeclared (first use in this function) iscsi_init.c:1130: (Each undeclared identifier is reported only once iscsi_init.c:1130: for each function it appears in.) make: *** [iscsi_init.o] Error 1 I've also tried the 3.6.2 version (with the appropriate linux-iscsi version) with the same result. Has anyone else seen similiar errors? Thanks, -Matt -- Clarke Consulting 100 Produce Ave., Suite E South San Francisco, CA 94080 cell/direct: 650-222-1538 office: 650-742-7790 fax: 650-745-3883 www.clarkeconsulting.com |
|
From: Davide D. <da...@sy...> - 2004-11-03 15:27:04
|
Hello, FYI: today I installed iscsi-init-3.6.2 with linux-iscsi-3.6.2 (kernel 2.4). I don't get errors during shutdown, it works perfectly! I didn't find yet a solution for iscsi-init-4.0.1.2 with linux-iscsi-4.0.1.10 (kernel 2.6). Regards, Davide Diana On Tue, 2004-11-02 at 12:10, Davide Diana wrote: > Hello, > I don't shutdown the ethernet in runlevels 6 and 0, I used a trick in my > /etc/network/interfaces. > I changed also in /etc/init.d the line "halt -i -d -f $poweroff $hddown" > in "halt -d -f $poweroff $hddown". Obviously I did the same thing in my > /etc/init.d/reboot script since the -i switch shuts down all the network > interfaces. > Unfortunately the problem persists, I tried to get a shell just before > the system executes the command "halt -d -f -p" (this is the last > command the system executes before reboot) in order to understand what's > happen: Here I can't see the error yet and the filesystem is still > writeable then as soon as I launch the command "halt -d -f -p" I get the > error and the system reboots. Please note that if I launch "halt -d -f" > omitting the -p switch I get immediately the error but I can continue to > work in my shell but the filesystem is "offline" and I get an error for > every command I launch. It seems that as soon as I launch "halt -d -f" > the kernel unloads the iscsi_sfnet module but there are some pending > operations that requires access to the filesystem. Is that possible? > > Thanks in Advance, > Davide > > P.S. These informations are for the 2.6 version of iscsi-init, I didn't > test the 2.4 version yet. > > > On Sun, 2004-10-31 at 03:38, James Harper wrote: > > Put the line: > > down /bin/false > > > > in your /etc/network/interfaces. It will prevent the interface actually being shut down. > > > > James > > > > ________________________________________ > > From: isc...@li... [mailto:isc...@li...] On Behalf Of Bryn Hughes > > Sent: Saturday, 30 October 2004 04:46 > > To: da...@sy... > > Cc: isc...@li... > > Subject: Re: [Iscsi-init-users] Shutdown problem... > > > > What I ended up doing on my systems was just removing Kxxnetwork from /etc/init.d/rc3.d and /etc/init.d/rc5.d - this means networking never actually gets shut down but the rest of the system goes down clean. This hasn't caused any problems for me and was extremely easy to implement. > > > > Bryn > > > > > > > > _______________________________ > > > > Bryn Hughes > > Network Specialist > > Information and Computing Services > > Vancouver Community College > > > > ph: (604) 443-8515 > > fax: (604) 443-8353 > > email: bh...@vc... > > _______________________________ > > > > >>>Igor Feoktistov <ig...@ne...> 10/29/04 10:49 am >>> > > > > Just check this article. > > > > > > http://sourceforge.net/mailarchive/forum.php?thread_id=5418545&forum_id=41734 > > > > > > There is more elegant solution with ifdown script, however. > > > > > > >From: Davide Diana <da...@sy...> > > > > >To: isc...@li... > > > > >X-Virus-Scanned: by amavisd-new-20030616-p9 at nethouse.it > > > > >Date: Fri, 29 Oct 2004 13:13:46 +0200 > > > > > > > > > >Hello, > > > > >I'm working with iscsi-init version 4.0.1.2 on two different hosts: I'm > > > > >having a problem during shutdown of both initiator computers. I tried to > > > > >work with linux-iscsi-4.0.1.9 (certified for this version of iscsi-init) > > > > >and also with linux-iscsi-4.0.1.10 (the new version) with no luck. I > > > > >attach the logs so you can see what happens: I sent two logs since I use > > > > >different filesystems on the two initiators: ext3, reiserfs. Obviously I > > > > >don't shutdown the ethernet connected to the target (IET) during halt > > > > >scripts. > > > > > > > > > >--- This is the part I'm referring to (taken from the ext3 log) --- > > > > > > > > > >iSCSI: releasing host0 > > > > >scsi0 (0:0): rejecting I/O to device being removed > > > > >scsi0 (0:0): rejecting I/O to device being removed > > > > >scsi0 (0:0): rejecting I/O to device being removed > > > > >EXT3-fs error (device sda2): ext3_find_entry: reading directory #31745 > > > > >offset 0 > > > > > > > > > >Synchronizing SCSI cache for disk sda: <4>FAILED > > > > > status = 0, message = 00, host = 0, driver = 08 > > > > > Info fld=0x0, Current sd: sense = f0 5 > > > > >ASC=20 ASCQ= 0 > > > > >Raw sense data:0xf0 0x00 0x05 0x00 0x00 0x00 0x00 0x06 0x00 0x00 0x00 > > > > >0x00 0x20 0x00 > > > > > > > > > >iSCSI: session iscsi bus 0 target id 0 to > > > > >iqn.2001-07.net.syndreams:blade-bay3.disk0 dropped > > > > >iSCSI: driver shutdown completed > > > > > > > > > >------------------------------------------------------------------- > > > > > > > > > >This don't cause problems after reboot, but I'd like to know if I'm > > > > >doing something wrong or if there is a way to avoid this. In your > > > > >opinion, can this cause problems? > > > > > > > > > > > > > > >Thanks in Advance, > > > > >Davide Diana > > > > > > > > > > > > > > > ------------------------------------------------------- > > > > This SF.Net email is sponsored by: > > > > Sybase ASE Linux Express Edition - download now for FREE > > > > LinuxWorld Reader's Choice Award Winner for best database on Linux. > > > > http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click > > > > > > Iscsi-init-users mailing list > > > > Isc...@li... > > > > https://lists.sourceforge.net/lists/listinfo/iscsi-init-users > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: > Sybase ASE Linux Express Edition - download now for FREE > LinuxWorld Reader's Choice Award Winner for best database on Linux. > http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click > _______________________________________________ > Iscsi-init-users mailing list > Isc...@li... > https://lists.sourceforge.net/lists/listinfo/iscsi-init-users |
|
From: Davide D. <da...@sy...> - 2004-11-02 11:10:13
|
Hello, I don't shutdown the ethernet in runlevels 6 and 0, I used a trick in my /etc/network/interfaces. I changed also in /etc/init.d the line "halt -i -d -f $poweroff $hddown" in "halt -d -f $poweroff $hddown". Obviously I did the same thing in my /etc/init.d/reboot script since the -i switch shuts down all the network interfaces. Unfortunately the problem persists, I tried to get a shell just before the system executes the command "halt -d -f -p" (this is the last command the system executes before reboot) in order to understand what's happen: Here I can't see the error yet and the filesystem is still writeable then as soon as I launch the command "halt -d -f -p" I get the error and the system reboots. Please note that if I launch "halt -d -f" omitting the -p switch I get immediately the error but I can continue to work in my shell but the filesystem is "offline" and I get an error for every command I launch. It seems that as soon as I launch "halt -d -f" the kernel unloads the iscsi_sfnet module but there are some pending operations that requires access to the filesystem. Is that possible? Thanks in Advance, Davide P.S. These informations are for the 2.6 version of iscsi-init, I didn't test the 2.4 version yet. On Sun, 2004-10-31 at 03:38, James Harper wrote: > Put the line: > down /bin/false > > in your /etc/network/interfaces. It will prevent the interface actually being shut down. > > James > > ________________________________________ > From: isc...@li... [mailto:isc...@li...] On Behalf Of Bryn Hughes > Sent: Saturday, 30 October 2004 04:46 > To: da...@sy... > Cc: isc...@li... > Subject: Re: [Iscsi-init-users] Shutdown problem... > > What I ended up doing on my systems was just removing Kxxnetwork from /etc/init.d/rc3.d and /etc/init.d/rc5.d - this means networking never actually gets shut down but the rest of the system goes down clean. This hasn't caused any problems for me and was extremely easy to implement. > > Bryn > > > > _______________________________ > > Bryn Hughes > Network Specialist > Information and Computing Services > Vancouver Community College > > ph: (604) 443-8515 > fax: (604) 443-8353 > email: bh...@vc... > _______________________________ > > >>>Igor Feoktistov <ig...@ne...> 10/29/04 10:49 am >>> > > Just check this article. > > > http://sourceforge.net/mailarchive/forum.php?thread_id=5418545&forum_id=41734 > > > There is more elegant solution with ifdown script, however. > > > >From: Davide Diana <da...@sy...> > > >To: isc...@li... > > >X-Virus-Scanned: by amavisd-new-20030616-p9 at nethouse.it > > >Date: Fri, 29 Oct 2004 13:13:46 +0200 > > > > > >Hello, > > >I'm working with iscsi-init version 4.0.1.2 on two different hosts: I'm > > >having a problem during shutdown of both initiator computers. I tried to > > >work with linux-iscsi-4.0.1.9 (certified for this version of iscsi-init) > > >and also with linux-iscsi-4.0.1.10 (the new version) with no luck. I > > >attach the logs so you can see what happens: I sent two logs since I use > > >different filesystems on the two initiators: ext3, reiserfs. Obviously I > > >don't shutdown the ethernet connected to the target (IET) during halt > > >scripts. > > > > > >--- This is the part I'm referring to (taken from the ext3 log) --- > > > > > >iSCSI: releasing host0 > > >scsi0 (0:0): rejecting I/O to device being removed > > >scsi0 (0:0): rejecting I/O to device being removed > > >scsi0 (0:0): rejecting I/O to device being removed > > >EXT3-fs error (device sda2): ext3_find_entry: reading directory #31745 > > >offset 0 > > > > > >Synchronizing SCSI cache for disk sda: <4>FAILED > > > status = 0, message = 00, host = 0, driver = 08 > > > Info fld=0x0, Current sd: sense = f0 5 > > >ASC=20 ASCQ= 0 > > >Raw sense data:0xf0 0x00 0x05 0x00 0x00 0x00 0x00 0x06 0x00 0x00 0x00 > > >0x00 0x20 0x00 > > > > > >iSCSI: session iscsi bus 0 target id 0 to > > >iqn.2001-07.net.syndreams:blade-bay3.disk0 dropped > > >iSCSI: driver shutdown completed > > > > > >------------------------------------------------------------------- > > > > > >This don't cause problems after reboot, but I'd like to know if I'm > > >doing something wrong or if there is a way to avoid this. In your > > >opinion, can this cause problems? > > > > > > > > >Thanks in Advance, > > >Davide Diana > > > > > > > > ------------------------------------------------------- > > This SF.Net email is sponsored by: > > Sybase ASE Linux Express Edition - download now for FREE > > LinuxWorld Reader's Choice Award Winner for best database on Linux. > > http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click > > > Iscsi-init-users mailing list > > Isc...@li... > > https://lists.sourceforge.net/lists/listinfo/iscsi-init-users |
|
From: James H. <Ja...@be...> - 2004-10-31 02:34:59
|
Put the line: down /bin/false in your /etc/network/interfaces. It will prevent the interface actually = being shut down. James ________________________________________ From: isc...@li... = [mailto:isc...@li...] On Behalf Of Bryn = Hughes Sent: Saturday, 30 October 2004 04:46 To: da...@sy... Cc: isc...@li... Subject: Re: [Iscsi-init-users] Shutdown problem... What I ended up doing on my systems was just removing Kxxnetwork from = /etc/init.d/rc3.d and /etc/init.d/rc5.d - this means networking never = actually gets shut down but the rest of the system goes down clean. = =A0This hasn't caused any problems for me and was extremely easy to = implement.=20 =A0 Bryn=20 =A0 _______________________________ Bryn Hughes=20 Network Specialist=20 Information and Computing Services=20 Vancouver Community College=20 ph: (604) 443-8515=20 fax: (604) 443-8353=20 email: bh...@vc...=20 _______________________________=20 >>>Igor Feoktistov <ig...@ne...> 10/29/04 10:49 am >>>=20 =A0 Just check this article.=20 =A0 =A0 http://sourceforge.net/mailarchive/forum.php?thread_id=3D5418545&forum_id= =3D41734=20 =A0 =A0 There is more elegant solution with ifdown script, however.=20 =A0 =A0 >From: Davide Diana <da...@sy...>=20 =A0 >To: isc...@li...=20 =A0 >X-Virus-Scanned: by amavisd-new-20030616-p9 at nethouse.it=20 =A0 >Date: Fri, 29 Oct 2004 13:13:46 +0200=20 =A0 >=20 =A0 >Hello,=20 =A0 >I'm working with iscsi-init version 4.0.1.2 on two different hosts: I'm = =A0 >having a problem during shutdown of both initiator computers. I tried = to=20 =A0 >work with linux-iscsi-4.0.1.9 (certified for this version of = iscsi-init)=20 =A0 >and also with linux-iscsi-4.0.1.10 (the new version) with no luck. I=20 =A0 >attach the logs so you can see what happens: I sent two logs since I = use=20 =A0 >different filesystems on the two initiators: ext3, reiserfs. Obviously = I=20 =A0 >don't shutdown the ethernet connected to the target (IET) during halt=20 =A0 >scripts.=20 =A0 >=20 =A0 >--- This is the part I'm referring to (taken from the ext3 log) ---=20 =A0 >=20 =A0 >iSCSI: releasing host0=20 =A0 >scsi0 (0:0): rejecting I/O to device being removed=20 =A0 >scsi0 (0:0): rejecting I/O to device being removed=20 =A0 >scsi0 (0:0): rejecting I/O to device being removed=20 =A0 >EXT3-fs error (device sda2): ext3_find_entry: reading directory #31745=20 =A0 >offset 0=20 =A0 >=20 =A0 >Synchronizing SCSI cache for disk sda: <4>FAILED=20 =A0 >=A0status =3D 0, message =3D 00, host =3D 0, driver =3D 08=20 =A0 >=A0Info fld=3D0x0, Current sd: sense =3D f0=A0=A05=20 =A0 >ASC=3D20 ASCQ=3D 0=20 =A0 >Raw sense data:0xf0 0x00 0x05 0x00 0x00 0x00 0x00 0x06 0x00 0x00 0x00=20 =A0 >0x00 0x20 0x00=20 =A0 >=20 =A0 >iSCSI: session iscsi bus 0 target id 0 to=20 =A0 >iqn.2001-07.net.syndreams:blade-bay3.disk0 dropped=20 =A0 >iSCSI: driver shutdown completed=20 =A0 >=20 =A0 >-------------------------------------------------------------------=20 =A0 >=20 =A0 >This don't cause problems after reboot, but I'd like to know if I'm=20 =A0 >doing something wrong or if there is a way to avoid this. In your=20 =A0 >opinion, can this cause problems?=20 =A0 >=20 =A0 >=20 =A0 >Thanks in Advance,=20 =A0 >Davide Diana=20 =A0 >=20 =A0 =A0 =A0 =A0 -------------------------------------------------------=20 =A0 This SF.Net email is sponsored by:=20 =A0 Sybase ASE Linux Express Edition - download now for FREE=20 =A0 LinuxWorld Reader's Choice Award Winner for best database on Linux.=20 =A0 http://ads.osdn.com/?ad_id=3D5588&alloc_id=3D12065&op=3Dclick=20 =A0 =A0 Iscsi-init-users mailing list=20 =A0 Isc...@li...=20 =A0 https://lists.sourceforge.net/lists/listinfo/iscsi-init-users=20 |
|
From: Bryn H. <bh...@vc...> - 2004-10-29 18:46:29
|
What I ended up doing on my systems was just removing Kxxnetwork from /etc/init.d/rc3.d and /etc/init.d/rc5.d - this means networking never actually gets shut down but the rest of the system goes down clean. This hasn't caused any problems for me and was extremely easy to implement. Bryn _______________________________ Bryn Hughes Network Specialist Information and Computing Services Vancouver Community College ph: (604) 443-8515 fax: (604) 443-8353 email: bh...@vc... _______________________________ >>>Igor Feoktistov <ig...@ne...> 10/29/04 10:49 am >>> Just check this article. http://sourceforge.net/mailarchive/forum.php?thread_id=5418545&forum_id=41734 There is more elegant solution with ifdown script, however. >From: Davide Diana <da...@sy...> >To: isc...@li... >X-Virus-Scanned: by amavisd-new-20030616-p9 at nethouse.it >Date: Fri, 29 Oct 2004 13:13:46 +0200 > >Hello, >I'm working with iscsi-init version 4.0.1.2 on two different hosts: I'm >having a problem during shutdown of both initiator computers. I tried to >work with linux-iscsi-4.0.1.9 (certified for this version of iscsi-init) >and also with linux-iscsi-4.0.1.10 (the new version) with no luck. I >attach the logs so you can see what happens: I sent two logs since I use >different filesystems on the two initiators: ext3, reiserfs. Obviously I >don't shutdown the ethernet connected to the target (IET) during halt >scripts. > >--- This is the part I'm referring to (taken from the ext3 log) --- > >iSCSI: releasing host0 >scsi0 (0:0): rejecting I/O to device being removed >scsi0 (0:0): rejecting I/O to device being removed >scsi0 (0:0): rejecting I/O to device being removed >EXT3-fs error (device sda2): ext3_find_entry: reading directory #31745 >offset 0 > >Synchronizing SCSI cache for disk sda: <4>FAILED > status = 0, message = 00, host = 0, driver = 08 > Info fld=0x0, Current sd: sense = f0 5 >ASC=20 ASCQ= 0 >Raw sense data:0xf0 0x00 0x05 0x00 0x00 0x00 0x00 0x06 0x00 0x00 0x00 >0x00 0x20 0x00 > >iSCSI: session iscsi bus 0 target id 0 to >iqn.2001-07.net.syndreams:blade-bay3.disk0 dropped >iSCSI: driver shutdown completed > >------------------------------------------------------------------- > >This don't cause problems after reboot, but I'd like to know if I'm >doing something wrong or if there is a way to avoid this. In your >opinion, can this cause problems? > > >Thanks in Advance, >Davide Diana > ------------------------------------------------------- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click Iscsi-init-users mailing list Isc...@li... https://lists.sourceforge.net/lists/listinfo/iscsi-init-users |
|
From: Igor F. <ig...@ne...> - 2004-10-29 17:49:54
|
Just check this article. http://sourceforge.net/mailarchive/forum.php?thread_id=5418545&forum_id=41734 There is more elegant solution with ifdown script, however. >From: Davide Diana <da...@sy...> >To: isc...@li... >X-Virus-Scanned: by amavisd-new-20030616-p9 at nethouse.it >Date: Fri, 29 Oct 2004 13:13:46 +0200 > >Hello, >I'm working with iscsi-init version 4.0.1.2 on two different hosts: I'm >having a problem during shutdown of both initiator computers. I tried to >work with linux-iscsi-4.0.1.9 (certified for this version of iscsi-init) >and also with linux-iscsi-4.0.1.10 (the new version) with no luck. I >attach the logs so you can see what happens: I sent two logs since I use >different filesystems on the two initiators: ext3, reiserfs. Obviously I >don't shutdown the ethernet connected to the target (IET) during halt >scripts. > >--- This is the part I'm referring to (taken from the ext3 log) --- > >iSCSI: releasing host0 >scsi0 (0:0): rejecting I/O to device being removed >scsi0 (0:0): rejecting I/O to device being removed >scsi0 (0:0): rejecting I/O to device being removed >EXT3-fs error (device sda2): ext3_find_entry: reading directory #31745 >offset 0 > >Synchronizing SCSI cache for disk sda: <4>FAILED > status = 0, message = 00, host = 0, driver = 08 > Info fld=0x0, Current sd: sense = f0 5 >ASC=20 ASCQ= 0 >Raw sense data:0xf0 0x00 0x05 0x00 0x00 0x00 0x00 0x06 0x00 0x00 0x00 >0x00 0x20 0x00 > >iSCSI: session iscsi bus 0 target id 0 to >iqn.2001-07.net.syndreams:blade-bay3.disk0 dropped >iSCSI: driver shutdown completed > >------------------------------------------------------------------- > >This don't cause problems after reboot, but I'd like to know if I'm >doing something wrong or if there is a way to avoid this. In your >opinion, can this cause problems? > > >Thanks in Advance, >Davide Diana > |
|
From: Davide D. <da...@sy...> - 2004-10-29 11:13:58
|
Hello, I'm working with iscsi-init version 4.0.1.2 on two different hosts: I'm having a problem during shutdown of both initiator computers. I tried to work with linux-iscsi-4.0.1.9 (certified for this version of iscsi-init) and also with linux-iscsi-4.0.1.10 (the new version) with no luck. I attach the logs so you can see what happens: I sent two logs since I use different filesystems on the two initiators: ext3, reiserfs. Obviously I don't shutdown the ethernet connected to the target (IET) during halt scripts. --- This is the part I'm referring to (taken from the ext3 log) --- iSCSI: releasing host0 scsi0 (0:0): rejecting I/O to device being removed scsi0 (0:0): rejecting I/O to device being removed scsi0 (0:0): rejecting I/O to device being removed EXT3-fs error (device sda2): ext3_find_entry: reading directory #31745 offset 0 Synchronizing SCSI cache for disk sda: <4>FAILED status = 0, message = 00, host = 0, driver = 08 Info fld=0x0, Current sd: sense = f0 5 ASC=20 ASCQ= 0 Raw sense data:0xf0 0x00 0x05 0x00 0x00 0x00 0x00 0x06 0x00 0x00 0x00 0x00 0x20 0x00 iSCSI: session iscsi bus 0 target id 0 to iqn.2001-07.net.syndreams:blade-bay3.disk0 dropped iSCSI: driver shutdown completed ------------------------------------------------------------------- This don't cause problems after reboot, but I'd like to know if I'm doing something wrong or if there is a way to avoid this. In your opinion, can this cause problems? Thanks in Advance, Davide Diana |
|
From: Igor F. <ife...@ya...> - 2004-10-03 19:17:10
|
It does not have to be a module. Userspace iscsi-init is in my plan. But I think I'll keep module version because of /proc/net/pnp. >Does it have to be a module? A simple 'iscsi-init' tool that runs from >userspace should be able to do what the iscsi-init module does. Before I >found out that iscsi-init existed, I thought of creating a very cut down >iscsid that just set up the connection and then died. With such a tool + >ifconfig I'd be able to do what I'm doing now, although if I wanted to >do dhcp it would be a bit more complicated. The nice thing about >iscsi-init is that it's all rolled into one but that sounds like what >Manish was objecting to. It would also be a bit harder to get it into >initrd automatically but I already need to create the device node via >script. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com |
22 messages has been excluded from this view by a project administrator.
