https://bugs.kde.org/show_bug.cgi?id=402660
Nate Graham changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
Severity|major
https://bugs.kde.org/show_bug.cgi?id=402660
ak...@iname.com changed:
What|Removed |Added
CC||ak...@iname.com
--- Comment #39 from ak...@ina
https://bugs.kde.org/show_bug.cgi?id=402660
soredake changed:
What|Removed |Added
CC||ndrzj1...@relay.firefox.com
--
You are receiving th
https://bugs.kde.org/show_bug.cgi?id=402660
--- Comment #38 from Mihai Sorin Dobrescu ---
An idea: what if the devices under same controller are grouped under a tree
node and a device can be mounted/unmounted by clicking on it's button and the
controller itself by clicking on it's own button?
Wha
https://bugs.kde.org/show_bug.cgi?id=402660
Nate Graham changed:
What|Removed |Added
CC||ro...@kde.org
--- Comment #37 from Nate Graham -
https://bugs.kde.org/show_bug.cgi?id=402660
Nate Graham changed:
What|Removed |Added
Keywords||usability
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=402660
--- Comment #36 from Mihai Sorin Dobrescu ---
Well, the most annoying is, I realize now, when I need to scan a disk - so it
goes away at unmount.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=402660
--- Comment #35 from Stuart K. Smith ---
Still not resolved.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=402660
--- Comment #34 from Christoph Feck ---
*** Bug 414906 has been marked as a duplicate of this bug. ***
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=402660
--- Comment #33 from David Edmundson ---
FWIW, I withdraw my original comment in #5
>From the kernel ioctl udisks calls
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=253e05724f9230910344357b1142ad8642ff9f5a
it very muc
https://bugs.kde.org/show_bug.cgi?id=402660
--- Comment #32 from Stuart K. Smith ---
Mihai Sorin Dobrescu: I totally got what you meant and my comment wasn't
pointed at you. Rather, I was try to illustrate a broader point that different
devices needs different actions and the terms are important
https://bugs.kde.org/show_bug.cgi?id=402660
--- Comment #31 from Mihai Sorin Dobrescu ---
(In reply to Stuart K. Smith from comment #26)
Right, sorry I was careless about terminology, this discussion began after all
from the wonderful Linux flexibility of mounting and unmounting disks so blamed
b
https://bugs.kde.org/show_bug.cgi?id=402660
--- Comment #30 from Christoph Feck ---
hdparm is for spinning disks. It doesn't unmount, but sends a direct IDE/SATA
command to the disk.
Different needs for different device types...
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=402660
--- Comment #29 from Stuart K. Smith ---
That doesn't seem to work here, at least not with a USB stick:
sudo hdparm -y /dev/sdi
[sudo] password for stuart:
/dev/sdi:
issuing standby command
SG_IO: bad/missing sense data, sb[]: f0 00 05 00 00 00 00
https://bugs.kde.org/show_bug.cgi?id=402660
--- Comment #28 from Christoph Feck ---
People have long requested to power-down-on-remove, see bug 270808. The problem
is the way the power-down is done. May be an udisk2 bug.
When I use the 'hdparm -y /dev/sdX' command, the disk is powered down, but
https://bugs.kde.org/show_bug.cgi?id=402660
--- Comment #27 from Stuart K. Smith ---
Thinking it over, what I would like to see is;
If the USB storage device is a CD/DVD/BR, "Eject" is the default action.
If the device is a USB attached file system but not a CD/DVD/BR, then set
"Unmount all fil
https://bugs.kde.org/show_bug.cgi?id=402660
--- Comment #26 from Stuart K. Smith ---
Agreed, however in the case of USB thumb drive, unmounting forces commit or it
won't unmount until cache is clear. It least that's my belief. IME I can't
unmount any file system until it's not being used.
Part o
https://bugs.kde.org/show_bug.cgi?id=402660
--- Comment #25 from Mihai Sorin Dobrescu ---
For me there is one more thing important: to be able to eject "logically" with
the insurance of data fully written on it. Then to be able to eject it for
"physical" eject - unplug, with the insurance of data
https://bugs.kde.org/show_bug.cgi?id=402660
--- Comment #24 from Stuart K. Smith ---
There seems to be a lot of rambling on this bug report about loosely related
topics. My issue is that a USB device should not have to be unplugged and
re-inserted by design. That is a very poor working practice.
https://bugs.kde.org/show_bug.cgi?id=402660
Kai Uwe Broulik changed:
What|Removed |Added
CC||stuartksm...@gmail.com
--- Comment #23 from K
https://bugs.kde.org/show_bug.cgi?id=402660
Patrick Silva changed:
What|Removed |Added
CC||ash...@linuxcomp.ru
--- Comment #22 from Patric
https://bugs.kde.org/show_bug.cgi?id=402660
Christoph Feck changed:
What|Removed |Added
CC||torokhov_...@mail.ru
--- Comment #21 from Chri
https://bugs.kde.org/show_bug.cgi?id=402660
Christoph Feck changed:
What|Removed |Added
CC||p...@gmx.de
--- Comment #20 from Christoph Fec
https://bugs.kde.org/show_bug.cgi?id=402660
Nate Graham changed:
What|Removed |Added
CC||cf...@kde.org
--- Comment #19 from Nate Graham -
https://bugs.kde.org/show_bug.cgi?id=402660
--- Comment #18 from Mihai Sorin Dobrescu ---
One more question: Assuming I have a multiple disk enclosure, mounting two
disks, ejecting disk A, then B, will flush and ensure the disk A (first
ejected) is in the full written state too, along with the la
https://bugs.kde.org/show_bug.cgi?id=402660
--- Comment #17 from Mihai Sorin Dobrescu ---
I have a supplemental issue related to this.
Some disks go to sleep after a while (WD Green type).
At this point, I can't revive them unless a power down them occurs.
At this point, the disks are mounted fr
https://bugs.kde.org/show_bug.cgi?id=402660
--- Comment #16 from Mihai Sorin Dobrescu ---
Backend functionality is important for the reason of the current behaviour, but
I think the mounting unavailability is the main issue for the user. Thinking of
not IT related persons, they won't even care an
https://bugs.kde.org/show_bug.cgi?id=402660
--- Comment #15 from Nate Graham ---
Similar, but not actually the same issue. That one's about the display in the
Devices Notifier Widget, but this bug is about what's going on on the backend.
--
You are receiving this mail because:
You are watching
https://bugs.kde.org/show_bug.cgi?id=402660
Patrick Silva changed:
What|Removed |Added
CC||bugsefor...@gmx.com
--- Comment #14 from Patric
https://bugs.kde.org/show_bug.cgi?id=402660
--- Comment #13 from Mihai Sorin Dobrescu ---
A new question, after thinking at the power down vs. keeping it online by
simply unmounting. I see two cases:
- power on the enclosure, the available disks are listed, not yet mounted
- mount at least two by
https://bugs.kde.org/show_bug.cgi?id=402660
--- Comment #12 from Mihai Sorin Dobrescu ---
Tell that to a simple user. Even though would go in that config, the content
will scare him. Some option should be in the UI.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=402660
--- Comment #11 from Stefan Brüns ---
(In reply to Mihai Sorin Dobrescu from comment #9)
> Right, still, had no corruption before - was there an other method?
> Still, I need to mount/unmount separately than powering off.
> As any other disk or data sto
https://bugs.kde.org/show_bug.cgi?id=402660
--- Comment #10 from Mihai Sorin Dobrescu ---
Also, "then requesting that in-flight buffers and caches are committed to
stable storage" should be done on any unmount or whatever similar operation,
not for powering down only. If the data stream is cut, s
https://bugs.kde.org/show_bug.cgi?id=402660
--- Comment #9 from Mihai Sorin Dobrescu ---
Right, still, had no corruption before - was there an other method?
Still, I need to mount/unmount separately than powering off.
As any other disk or data storage.
And I have one tat I can never eject without
https://bugs.kde.org/show_bug.cgi?id=402660
--- Comment #8 from Stefan Brüns ---
(In reply to David Edmundson from comment #5)
> @Nate
>
> "
> . For drives connected through USB, the effect is that the USB device will
> be deconfigured followed by disabling the upstream hub port it is connected
https://bugs.kde.org/show_bug.cgi?id=402660
Nate Graham changed:
What|Removed |Added
Status|RESOLVED|REPORTED
Version|master
36 matches
Mail list logo
