"Seymour, Shane M" writes:
> Both of those things would have to be futures and require discussion -
> the very original version cleared stats on a device open but I got
> asked to keep it the stats cumulative so they would be more similar to
> disk stats.
Yes, this is a futures question. But in
One feature of tape statistics is that they're as much about the *tape*
as they are about the *drive*, which is uncommon for block devices. It
might be useful to have a set of counters which is cleared every time a
new tape is inserted into the drive. In particular, "bad reads since
this tape was
> From: Chris Friesen
> Also, I think it's wrong for filesystems and userspace to use it for
> alignment. In E.4 and E.5 in the "sbc3r25.pdf" doc, it looks like they
> use the optimal granularity field for alignment, not the optimal
> transfer length.
Everything you say suggests that "optima
> From: James Bottomley
>
> We really don't want to make the decision within the kernel of whether
> we believe the partition size or the disk capacity. For these disk
> problems we need it to be the former, but if we choose that always,
> we'll get weird results on mispartitioned devices.
>
>
> From: "Theodore Ts'o"
>
> On Wed, Nov 05, 2014 at 05:07:48PM +0100, James Bottomley wrote:
> >
> > OK, but I still don't understand how windows gets the partition table on
> > there in the first place ... that must surely be some sort of guess the
> > disk size hack.
>
> 99% of the time the p
> From: Alan Stern
> I posted a patch to allow the user to override the reported capacity:
>
> http://marc.info/?l=linux-scsi&m=140993840113445&w=2
I see the patch, and I feel confident I could install it if I needed
to. What command do I execute to "write to the capacity_override
attrib
Replying to two messages at once:
> Date: Tue, 4 Nov 2014 11:14:39 -0500 (EST)
> From: Alan Stern
> cc: "Dale R. Worley" , ,
>
>
> On Tue, 4 Nov 2014, James Bottomley wrote:
>
> > On Mon, 2014-11-03 at 16:06 -0500, Dale R. Worley wrote:
> >
Was there any resolution as to how large disk drives would be handled
if their interface did not support the "capacity" request that would
tell how large they were?
Or as an alternative, is there any way to avoid buying USB-SCSI
interfaces that do not support the large-capacity request?
Unfortunat
> From: James Bottomley
> Before we embark on elaborate hacks, why don't we just make the capacity
> writeable (by root) in sysfs from userspace (will require block change)?
> We can then encode all the nasty heuristics (including gpt reading) in
> userspace as a udev rule.
Looking in from the o
> From: Alan Stern
> Anyway, I can try writing a patch to add this capability. We'll see if
> it can solve your problem.
Unfortunately, I think there is genuine value in such a hack. E.g.,
I've got two USB-to-SATA adapters. One works correctly. One does
not. But at this point, I can't atta
> From: Alan Stern
>
> On Fri, 29 Aug 2014, Matthew Dharm wrote:
> > Is there an 'easy' way to override the detected size of a storage
> > device from userspace? If we had that, someone could write a helper
> > application which looked for this particular fubar and try to Do The
> > Right Thing(
> From: Alan Stern
> If you try to repartition the drive under Windows using the deficient
> adapter, you'll see that the problem still exists. It just doesn't
> show up during normal use.
So in summary, the Windows workaround is icky, but it allows any use
but repartitioning to be one on the
What I find interesting is that Windows (at least, Windows 7
Professional) seems to be able to handle the deficient adapter. What
I'd like to do is log the disk commands during the mounting sequence,
preferably at both the SCSI and USB layers. Then at least we'll know
exactly what the driver is d
> From: James Bottomley
> Did you try read capacity 16 on it? What happened? (the AS2105 rejects
> read capacity 16, so there's no reliable way to deduce the capacity of
> drives over 2TB).
OK, I had to track down which package contains sg_readcap.
The adapter that fails gives this output:
e appended James Bottomley's response, to avoid creating an
additional message.
Dale
--
Date: Wed, 20 Aug 2014 16:18:00 -0400
From: wor...@alum.mit.edu (Dale R. Worley)
To: linux-scsi@vger.kernel.org
Subject: Problem with USB-to-SATA adapters
I don't know if this is the correct
I don't know if this is the correct place for this problem, but you
people can probably tell me the correct place.
I have two "USB to SATA adapter" dongles. In general, they work fine.
However I've discovered that one of them handles large (1 TB and
above) drives correctly and one does not. In p
> From: joystick
>
> I don't really understand this disk cache thing.
> Suppose a disk with write cache enabled of writeback type: Linux
> receives a write completed notification (a message from the disk) when
> the data has reached the cache of the disk. Correct? At that point it is
> not con
> From: joystick
>
> I don't really understand this disk cache thing.
> Suppose a disk with write cache enabled of writeback type: Linux
> receives a write completed notification (a message from the disk) when
> the data has reached the cache of the disk. Correct? At that point it is
> not con
Are ANSI-formatted tapes used on Linux? That is, tapes that contain
multiple files and use the the ANSI (= ECMA-13) tape labels. My
uderstanding is that a lot of the modern cartridge tapes record only
fixed-length blocks and/or that is how they are always used these
days.
Dale
--
To unsubscribe
This thread leads me to ask: Do people use ANSI-formatted tapes any
more? That is, tape volumes with miltiple files, header and trailer
labels, etc.?
Dale
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majord...@vger.kernel.org
More majordomo
> From: "Dr. Greg Wettstein"
> If there is an issue it would seem to be in the best interests of
> those of us committed to open-source storage solutions to understand
> and protect ourselves from the situation. There is a third saying
> which is important as well:
If the question is a legitima
(This is based on the bug report
https://bugzilla.redhat.com/show_bug.cgi?id=918200)
When I repartition a disk, when I exit the partitioning tool, it has
some method of ordering the kernel to re-read the partition table.
Thus, after repartitioning, the partitions I've created/changed are
available
22 matches
Mail list logo
