From owner-freebsd-scsi@FreeBSD.ORG Sun Feb 1 15:57:30 2015 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id DBD3B9B0 for ; Sun, 1 Feb 2015 15:57:30 +0000 (UTC) Received: from mail-pa0-x243.google.com (mail-pa0-x243.google.com [IPv6:2607:f8b0:400e:c03::243]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A594137E for ; Sun, 1 Feb 2015 15:57:30 +0000 (UTC) Received: by mail-pa0-f67.google.com with SMTP id eu11so38879498pac.2 for ; Sun, 01 Feb 2015 07:57:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:from:to:subject:date:mime-version:content-type :thread-index:content-language; bh=YWVUYrgj4WTemOAoVc+jSYjNPQYY5jsDmKfosmQW6So=; b=KoRjXqyUOyI6/6+Bs9QBrDRjhJvObG9U44Akpc+nnLx5+EhDUPWq9qyw8ux1KfodlG uqkpR4yEGRV4eqXRzBD0Ok6oIui47I7IHq9heBUq8RBcgjf+NHrY5S7WTmqMJ/TzGcYd 1omcMz3jvUr0ATrBPzev9qCUMvzOtlsnJz2GR1eNaiTkBbjnLgB/RV/q3dJBlk+V43nZ ndHANewN8VRqA/9qEEcx42w4EbdpBdrTSvvhjtCl62eQM5LAb8zqPyLfyquthVRxnwXG F47bpHOhNGCW9WtM32hKNJIlNZSn2Y5P9Q5GW+iNnW40U0nElGUNOIQw1jXpaBkTy7CR ZxFQ== X-Received: by 10.66.254.232 with SMTP id al8mr23249126pad.76.1422806250234; Sun, 01 Feb 2015 07:57:30 -0800 (PST) Received: from jitendra19f750 ([106.223.151.184]) by mx.google.com with ESMTPSA id w9sm16358384pbt.10.2015.02.01.07.57.27 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Sun, 01 Feb 2015 07:57:29 -0800 (PST) Message-ID: <54ce4ce9.8944440a.1e15.ffffa875@mx.google.com> X-Google-Original-Message-ID: <010e01d03e37$cb386ae0$61a940a0$@seocompany11@gmail.com> From: "Shalu" To: Subject: Guaranteed 1st t Page on Google Ranking..! Date: Sun, 1 Feb 2015 21:27:13 +0530 MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AdA+NeI/JgAEPpWNTzObIY12H3uCag== Content-Language: en-us Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Feb 2015 15:57:30 -0000 Hello, We are a leading result oriented Web Solutions Company in India and we are doing this from last 6 years for many SEO agency based in USA, UK, Canada and Australia. We do all our work in an organic basis so that our clients get a permanent result. We will be optimizing your website in the major search engines like Google, Yahoo & Bing which results in improvements in keyword ranking, traffic & link popularity. Our SEO works helps your website in following ways: 1. Complete SEO Package &Keyword Analysis 2. Competitor Analysis 3. SEO Analysis report 4. Finding & fixing all the technical errors from the website 5. On-page optimization (Designing stuff) 6. Adding landing pages if required. 7. Social Media Optimization etc 8. Off page optimization (Promotional stuff with other website to get quality Back links). 9. Content Writing 10. Reputation management. Our website design expert team will provide you the best service and support We can provide you 1st to 10th position in Google rankings at very affordable prices. Email us back to get a full proposal. Regards! Marketing Executive Note: I am not spamming. I have studied your website and believe I can help with your business promotion. If you still want us to not contact you, you can ignore this email and I will not contact again. From owner-freebsd-scsi@FreeBSD.ORG Thu Feb 5 22:38:29 2015 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 03EAC765 for ; Thu, 5 Feb 2015 22:38:29 +0000 (UTC) Received: from mithlond.kdm.org (mithlond.kdm.org [70.56.43.85]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "A1-33714", Issuer "A1-33714" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 9E583925 for ; Thu, 5 Feb 2015 22:38:28 +0000 (UTC) Received: from mithlond.kdm.org (localhost [127.0.0.1]) by mithlond.kdm.org (8.14.9/8.14.9) with ESMTP id t15McQYb016841 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 5 Feb 2015 15:38:26 -0700 (MST) (envelope-from ken@mithlond.kdm.org) Received: (from ken@localhost) by mithlond.kdm.org (8.14.9/8.14.9/Submit) id t15McQaR016840; Thu, 5 Feb 2015 15:38:26 -0700 (MST) (envelope-from ken) Date: Thu, 5 Feb 2015 15:38:26 -0700 From: "Kenneth D. Merry" To: Peter Xu Subject: Re: bugfix: SA driver will unwind when close device even with SA_MODE_NOREWIND Message-ID: <20150205223826.GA16679@mithlond.kdm.org> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (mithlond.kdm.org [127.0.0.1]); Thu, 05 Feb 2015 15:38:26 -0700 (MST) X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS autolearn=ham autolearn_force=no version=3.4.0 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on mithlond.kdm.org Cc: freebsd-scsi@freebsd.org X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Feb 2015 22:38:29 -0000 On Fri, Jan 30, 2015 at 13:55:17 +0800, Peter Xu wrote: > Hi, > > In BSD system, when tape devices are discovered, CAM will create specific > /dev/saX.[0-3] automatically. Here when we does not the tape to auto rewind > when closing the device, we should access /dev/saX.1 (which means we are > using SA_MODE_NOREWIND mode). > > Found one bug that tape will auto rewind even accessing /dev/saX.1. That isn't a bug, it is the way things are supposed to work. The minor device terminology in the man page may be a little confusing. The man page says: FILES /dev/[n][e]sa[0-9] general form: /dev/sa0 Rewind on close /dev/nsa0 No rewind on close /dev/esa0 Eject on close (if capable) /dev/sa0.ctl Control mode device (to examine state while another program is accessing the device, e.g.). The naming convention carries over to the /dev/[n][e]sa[0-9].[0-3] devices. If you want a non-rewound device, you would need to use /dev/nsaX, or /dev/nsaX.[0-3]. If you want the tape to be ejected, you would use the /dev/esaX.[0-3] device. The idea behind the .[0-3] devices was that they were to be for different possible tape drive densities. If you look at the output of 'mt status', it has output entries that could be filled with possible densities, but that aren't actually used. Just as the entries in 'mt status' aren't used, the .[0-3] entries are not used. There is no difference between those entries and the standard device names. I've considered removing the .[0-3] entries, since they are primarily just confusing for anyone who sees them. If anyone thinks we should keep them, let me know. Otherwise I may just take them out with the upcoming round of sa(4) driver changes. There are modern tape drives (e.g. IBM TS1140, TS1150) that are capable of writing at multiple densities, but I don't know that we need to necessarily let the user switch density by using a different device. You can also do a 'mt density X' and switch that way. Ken -- Kenneth Merry ken@FreeBSD.ORG From owner-freebsd-scsi@FreeBSD.ORG Fri Feb 6 04:07:02 2015 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 34454CD5; Fri, 6 Feb 2015 04:07:02 +0000 (UTC) Received: from mail-ig0-x232.google.com (mail-ig0-x232.google.com [IPv6:2607:f8b0:4001:c05::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EDDC5DEF; Fri, 6 Feb 2015 04:07:01 +0000 (UTC) Received: by mail-ig0-f178.google.com with SMTP id hl2so5100371igb.5; Thu, 05 Feb 2015 20:07:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=LTT8uzuXqmS25ZAYfeBW3Pya6lb/PxJMYZ7Zy+zS5Ow=; b=YUC5FiGch91YQ01zOzt4jL9eVUNCsqSh28K6iwTvbqfdgTaIomjsqjVNWgW8+W9LvK sAePNke0y9yX9XaHv02E5x7PHS0uUx5jr6GDgmPZAKZ9ceALYZR/7yYoKF9+qY24q45P qLEDnP9KOgzMSyS/44ut1sCie75/YH3T3a5H6QsvZNbDZN4kgrEXSw89kDG1rtmU1U+j SxxijY2odkCrQHXlZTq7iPWBS87ZUHMsovgv3mS91chYUhPABzwrQF4/9sIQwzef6DG/ gzNTr7KhAl5b46PczSRggo4UIbI1pgFUKwE2mLrAoTJ2ZJUUtpHctA4OyhkPqLi1hZCG esVg== MIME-Version: 1.0 X-Received: by 10.50.253.12 with SMTP id zw12mr304984igc.24.1423195621394; Thu, 05 Feb 2015 20:07:01 -0800 (PST) Received: by 10.107.53.77 with HTTP; Thu, 5 Feb 2015 20:07:01 -0800 (PST) In-Reply-To: <20150205223826.GA16679@mithlond.kdm.org> References: <20150205223826.GA16679@mithlond.kdm.org> Date: Fri, 6 Feb 2015 12:07:01 +0800 Message-ID: Subject: Re: bugfix: SA driver will unwind when close device even with SA_MODE_NOREWIND From: Peter Xu To: "Kenneth D. Merry" Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: freebsd-scsi@freebsd.org X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Feb 2015 04:07:02 -0000 I think I was misguided by the source code. In saregister() of scsi_sa.c, it might be confusing that the loop to create the .[0-3] devices are using SA_NUM_MODES: for (i = 0; i < SA_NUM_MODES; i++) { Thanks for the clarify. :) Peter On Fri, Feb 6, 2015 at 6:38 AM, Kenneth D. Merry wrote: > On Fri, Jan 30, 2015 at 13:55:17 +0800, Peter Xu wrote: > > Hi, > > > > In BSD system, when tape devices are discovered, CAM will create specific > > /dev/saX.[0-3] automatically. Here when we does not the tape to auto > rewind > > when closing the device, we should access /dev/saX.1 (which means we are > > using SA_MODE_NOREWIND mode). > > > > Found one bug that tape will auto rewind even accessing /dev/saX.1. > > That isn't a bug, it is the way things are supposed to work. The minor > device terminology in the man page may be a little confusing. > > The man page says: > > FILES > /dev/[n][e]sa[0-9] general form: > /dev/sa0 Rewind on close > /dev/nsa0 No rewind on close > /dev/esa0 Eject on close (if capable) > /dev/sa0.ctl Control mode device (to examine state while > another > program is accessing the device, e.g.). > > The naming convention carries over to the /dev/[n][e]sa[0-9].[0-3] devices. > > If you want a non-rewound device, you would need to use /dev/nsaX, or > /dev/nsaX.[0-3]. If you want the tape to be ejected, you would use the > /dev/esaX.[0-3] device. > > The idea behind the .[0-3] devices was that they were to be for different > possible tape drive densities. If you look at the output of 'mt status', > it has output entries that could be filled with possible densities, but > that aren't actually used. > > Just as the entries in 'mt status' aren't used, the .[0-3] entries are not > used. There is no difference between those entries and the standard device > names. > > I've considered removing the .[0-3] entries, since they are primarily just > confusing for anyone who sees them. If anyone thinks we should keep them, > let me know. Otherwise I may just take them out with the upcoming round of > sa(4) driver changes. > > There are modern tape drives (e.g. IBM TS1140, TS1150) that are capable > of writing at multiple densities, but I don't know that we need to > necessarily let the user switch density by using a different device. > You can also do a 'mt density X' and switch that way. > > Ken > -- > Kenneth Merry > ken@FreeBSD.ORG >