Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 3325C200C53 for ; Tue, 28 Mar 2017 02:02:46 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 31ADE160B9A; Tue, 28 Mar 2017 00:02:46 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 78A1E160B85 for ; Tue, 28 Mar 2017 02:02:45 +0200 (CEST) Received: (qmail 67618 invoked by uid 500); 28 Mar 2017 00:02:44 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 67607 invoked by uid 99); 28 Mar 2017 00:02:44 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 28 Mar 2017 00:02:44 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 360BD1812FA for ; Tue, 28 Mar 2017 00:02:44 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id McR0gwGEGpy7 for ; Tue, 28 Mar 2017 00:02:43 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id D97FD5FB40 for ; Tue, 28 Mar 2017 00:02:42 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 03D55E0596 for ; Tue, 28 Mar 2017 00:02:42 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id AE5D624066 for ; Tue, 28 Mar 2017 00:02:41 +0000 (UTC) Date: Tue, 28 Mar 2017 00:02:41 +0000 (UTC) From: "Chen Liang (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HDFS-11582) Block Storage : add SCSI target access daemon MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 28 Mar 2017 00:02:46 -0000 [ https://issues.apache.org/jira/browse/HDFS-11582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen Liang updated HDFS-11582: ------------------------------ Attachment: HDFS-11582-HDFS-7240.003.patch Thanks [~anu] for the review and the comments! addressed in v003 patch. bq. who ensures that we don't have race condition that is two volumeNames from 2 different CBlock servers are not racing here ? I understand that it is a pretty far fetched scenerio and I was wondering if the jscsi target server does any kind of concurrency control. This was written to make sure that mounting a volume twice or more would not reset the in-memory metadata. But just like you mentioned, jscsi code, or even system iscsi might already handled this scenario. This code is more like doing a safety check without assuming it will be handled. > Block Storage : add SCSI target access daemon > --------------------------------------------- > > Key: HDFS-11582 > URL: https://issues.apache.org/jira/browse/HDFS-11582 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: hdfs > Reporter: Chen Liang > Assignee: Chen Liang > Attachments: HDFS-11582-HDFS-7240.001.patch, HDFS-11582-HDFS-7240.002.patch, HDFS-11582-HDFS-7240.003.patch > > > This JIRA adds the daemon process that exposes SCSI target access. More specifically, with this daemon process running, any OS with SCSI can talk to this daemon process and treat CBlock volumes as SCSI targets, in this way the user can mount the volume just like the POSIX manner. -- This message was sent by Atlassian JIRA (v6.3.15#6346) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org