jaunty no longer has this
** Changed in: shadow (Ubuntu)
Status: New => Fix Released
--
login.defs references libpam-umask which is a obsolete package
https://bugs.launchpad.net/bugs/245210
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
The cleanup may actually be more than a wishlist item, because
login.defs wrongly points out not to set UMASK and has leaves it
commented out. (As was correct when pam_umask did not parse it.)
--
/etc/login.defs umask cleanup
https://bugs.launchpad.net/bugs/71295
You received this bug notificatio
Still no gksu functionality to run apps as a differnt user (other then root) in
ubuntu 9.04.
(i.e. no way to quickly check your own email on the computer running all
day at the reception with the account used by all the receptionists for
example.)
--
gksu to regular users broken
https://bugs.
Public bug reported:
Binary package hint: kdeadmin
All user/group managment tools have to rely on the adduser/useradd
mechanism.
But kuser is not even following the same rules when creating
users/groups.
** Affects: kdeadmin (Ubuntu)
Importance: Undecided
Status: New
--
kuser is
Public bug reported:
Binary package hint: kdeadmin
New homedirs get drwx-- permissions.
(Instead of honoring the default drwxr-xr-x adduser setting. It is not
using the adduser mechanism as stated by debian policy.)
** Affects: kdeadmin (Ubuntu)
Importance: Undecided
Status: N
Debian policy states: "Packages other than base-passwd must not modify
/etc/passwd, /etc/shadow, /etc/group or /etc/gshadow."
(http://www.debian.org/doc/debian-policy/ch-opersys.html#s9.2)
--
kuser ignores umask when creating homedirs
https://bugs.launchpad.net/bugs/379399
You received this bug n
Public bug reported:
Binary package hint: kdeadmin
kuser creates subdirecories in the homes, mimiking other OSes behaviour,
but /etc/skel is not used for this.
Instead /etc/skel might provide pub/, priv/ and incoming/ directories with
correct permissions.
And /home/groups/users/writable and /ho
Public bug reported:
Let groupadd have the option to create /home/group/ sgid directories.
Sgid group directories are the means for users to easily collaborate on
local files with the user private group scheme used in debian/ubuntu.
Graphical tools can then adopt to this addgroup option.
Debia
Public bug reported:
Binary package hint: user-setup
Set up a sgid /home/group/users directory for the "users" group if it
doesn't exist, so that users are provided with a way to collaborate on
local files.
This will also seed the answer of how smaller groups can collaborate.
For full control:
The following example might be further enhanced:
root:group (rwxrwsr-t) /home/share/
root:group (rwsrwsrwt) /home/share//incoming
root:group (rwxrwx---) /home/share//private
--
set up a /home/group/users directory
https://bugs.launchpad.net/bugs/379431
You received this bug notification because
The following example might be further enhanced:
root:group (rwxrwsr-t) /home/share/
root:group (rwsrwsrwt) /home/share//incoming
root:group (rwxrwx---) /home/share//private
--
Let groupadd create /home/group/ sgid directories
https://bugs.launchpad.net/bugs/379421
You received this bug notifica
Public bug reported:
Binary package hint: base-files
Please provide the directories /etc/skel/private (rwx--) and
/etc/skel/incoming with appropriate permissions.
In the user private group scheme used in debian/ubuntu the homedirs are
created with permissions allowing the users to share and
The following wiki page now contains more information and ties together related
bugs.
https://wiki.ubuntu.com/MultiUserManagement
--
pam_umask.so missing in common-session
https://bugs.launchpad.net/bugs/253096
You received this bug notification because you are a member of Ubuntu
Bugs, which is
The following wiki page now contains more information and ties together related
bugs.
https://wiki.ubuntu.com/MultiUserManagement
--
set up a /home/group/users directory
https://bugs.launchpad.net/bugs/379431
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
The following wiki page now contains more information and ties together related
bugs.
https://wiki.ubuntu.com/MultiUserManagement
--
remove/comment /etc/profile umask setting
https://bugs.launchpad.net/bugs/379341
You received this bug notification because you are a member of Ubuntu
Bugs, which
The following wiki page now contains more information and ties together related
bugs.
https://wiki.ubuntu.com/MultiUserManagement
--
provide some info about users and file permissions
https://bugs.launchpad.net/bugs/252351
You received this bug notification because you are a member of Ubuntu
Bu
The following wiki page now contains more information and ties together related
bugs.
https://wiki.ubuntu.com/MultiUserManagement
--
users not belonging to users group
https://bugs.launchpad.net/bugs/253103
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
The following wiki page now contains more information and ties together related
bugs.
https://wiki.ubuntu.com/MultiUserManagement
--
Let groupadd create /home/group/ sgid directories
https://bugs.launchpad.net/bugs/379421
You received this bug notification because you are a member of Ubuntu
Bug
The following wiki page now contains more information and ties together related
bugs.
https://wiki.ubuntu.com/MultiUserManagement
--
pam_umask is missing a pam-auth-profile
https://bugs.launchpad.net/bugs/379335
You received this bug notification because you are a member of Ubuntu
Bugs, which i
The following wiki page now contains more information and ties together related
bugs.
https://wiki.ubuntu.com/MultiUserManagement
--
gksu to regular users broken
https://bugs.launchpad.net/bugs/246192
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
The following wiki page now contains more information and ties together related
bugs.
https://wiki.ubuntu.com/MultiUserManagement
--
/etc/login.defs umask cleanup
https://bugs.launchpad.net/bugs/71295
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
*** This bug is a duplicate of bug 244844 ***
https://bugs.launchpad.net/bugs/244844
This pm-utils bug is not a duplicate of the laptop-mode-tools bug #244844.
This bug is about pm-utils provocing a conflict.
The other is about adapting laptop-mode-tools to the pm-utils / acpi-
support hook
** Summary changed:
- Adapt invocation to ubuntu acpi-support / pm-tools packages
+ Adapt laptop-mode-tools invocation to ubuntu's acpi-support / pm-tools
packages
** Description changed:
Binary package hint: laptop-mode-tools
+ Adaption would would mean to include scripts that call
+ "/us
I don't know.
I believe in letting pm-utils manage power state changes (if that is the
tool of choice) and letting acpi-support taking care of button, battery
and ac events etc.
A disk idleing tool like laptop-mode-tools can be hooked into these
appropriately, when its packaged with scripts that
A "howto get disks idleing correctly (without excessive load cycling)" has been
added to:
https://wiki.ubuntu.com/PowerManagement
--
High frequency of load/unload cycles on some hard disks may shorten lifetime
https://bugs.launchpad.net/bugs/59695
You received this bug notification because you a
There is now an overview about the related bugs in the wiki.
https://wiki.ubuntu.com/PowerManagement#head-ab94c99627b86e9fbb29a09d3316178269c3e764
--
Adapt laptop-mode-tools invocation to ubuntu's acpi-support / pm-tools packages
https://bugs.launchpad.net/bugs/244844
You received this bug notifi
There is now an overview about the related bugs in the wiki.
https://wiki.ubuntu.com/PowerManagement#head-ab94c99627b86e9fbb29a09d3316178269c3e764
--
missing hdparm -B setting during resume
https://bugs.launchpad.net/bugs/244833
You received this bug notification because you are a member of Ubunt
** Description changed:
This is not a support forum. Please do not use it as such (even though
it has been used as such already).
You can scan through the bug for links to the Ubuntu forums where many,
many different questions have been asked, answered, and re-answered.
The temporary
Then the bug is that acpi-support contains these bogus directories.
--
/etc/acpi/start.d and resume.d scripts are not run.
https://bugs.launchpad.net/bugs/244839
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing lis
There is now an overview about the related bugs in the wiki.
https://wiki.ubuntu.com/PowerManagement#head-ab94c99627b86e9fbb29a09d3316178269c3e764
--
laptop-mode needs to be activated in two places
https://bugs.launchpad.net/bugs/244838
You received this bug notification because you are a member
There is now an overview about the related bugs in the wiki.
https://wiki.ubuntu.com/PowerManagement#head-ab94c99627b86e9fbb29a09d3316178269c3e764
--
/etc/acpi/power.sh overrides user settings
https://bugs.launchpad.net/bugs/244836
You received this bug notification because you are a member of Ub
There is now an overview about the related bugs in the wiki.
https://wiki.ubuntu.com/PowerManagement#head-ab94c99627b86e9fbb29a09d3316178269c3e764
--
/etc/acpi/power.sh overrides user settings
https://bugs.launchpad.net/bugs/244836
You received this bug notification because you are a member of Ub
There is now an overview about the related bugs in the wiki.
https://wiki.ubuntu.com/PowerManagement#head-ab94c99627b86e9fbb29a09d3316178269c3e764
--
missing hdparm -B setting during boot
https://bugs.launchpad.net/bugs/244832
You received this bug notification because you are a member of Ubuntu
There is now an overview about the related bugs in the wiki.
https://wiki.ubuntu.com/PowerManagement#head-ab94c99627b86e9fbb29a09d3316178269c3e764
--
/etc/acpi/power.sh overrides user scripts
https://bugs.launchpad.net/bugs/244831
You received this bug notification because you are a member of Ubu
There is now an overview about the related bugs in the wiki.
https://wiki.ubuntu.com/PowerManagement#head-ab94c99627b86e9fbb29a09d3316178269c3e764
--
/etc/acpi/power.sh overrides user scripts
https://bugs.launchpad.net/bugs/244831
You received this bug notification because you are a member of Ubu
*** This bug is a duplicate of bug 244844 ***
https://bugs.launchpad.net/bugs/244844
See https://wiki.ubuntu.com/PowerManagement#head-
ab94c99627b86e9fbb29a09d3316178269c3e764 for the links between the
separate bugs.
--
pm-utils has laptop-tools script which conflicts with laptop-mode-tools
** Description changed:
This is not a support forum. Please do not use it as such (even though
it has been used as such already).
You can scan through the bug for links to the Ubuntu forums where many,
many different questions have been asked, answered, and re-answered.
- The temporary
Public bug reported:
Binary package hint: gksu
In (x)ubuntu 8.04 it ist not possible to run an application as a different
regular user with gksu.
A simple test:
Inserting the following line into /etc/sudoers (with visudo)
user ALL=(otheruser) ALL
leads to:
[EMAIL PROTECTED]:~$ gksu -
An "echo 1 >/sys/bus/usb/devices/.../power/persist" could be done for
usb-storage devices?
A pointer to kernel info:
http://www.mjmwired.net/kernel/Documentation/usb/persist.txt
and fix released bug #197166 "persist mode in hardy kernel"
--
Mounts external USB hard drive in a different point
The CONFIG_USB_PERSIST feature should probably be made to also check the serial
numbers of the devices it has been enabled for.
Because it is quite likely that one user or tow friends may have two disks of
same manufacturer and type.
(Especially in HotplugRaid laptop setups https://wiki.ubuntu
I am sorry my comments have been misunderstandable and caused this bug to be
set to invalid even if it may be valid.
My first comment was made to point to solution, that is possible with new
kernels.
The second to point out that USB_PERSIST should better be patched to check USB
IDs when somone
My comments did not describe an implemented design, but pointed to a
possibility to fix this in ubuntu.
** Changed in: linux (Ubuntu)
Status: Invalid => Confirmed
--
Mounts external USB hard drive in a different point after resuming sleep
https://bugs.launchpad.net/bugs/230671
You receive
To fix the issue the md, cryptsetup, etc. scripts that set up the root device
need to wait for their device to get set up by udev and timeout after a while
(possibly running a degraded raid).
https://wiki.ubuntu.com/HotplugRaid
https://wiki.ubuntu.com/BootDegradedRaid
--
initramfs-tools scrip
** Changed in: initramfs-tools (Ubuntu)
Status: New => Confirmed
--
Volume group containing encrypted root not initialized if device is slow to
appear
https://bugs.launchpad.net/bugs/247153
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
IMHO the cryptsetup scripts in initramfs should go into a waiting loop (0.5 sec
intervals) for their devices (going on quickly when device is available) and
timeout after a while.
Lets get rid of long sleep workarounds and race conditions.
** Summary changed:
- Volume group containing encrypt
Alternatively cryptsetup may be handled by udev rules, similar as md and
lvm devices are.
--
encrypted root initialisation does not wait for its device to appear
https://bugs.launchpad.net/bugs/247153
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
md and lvm devices are actually handled by udev rules.
For one, cryptsetup handling needs go into a waiting loop (Bug #247153),
or also be handled by udev rules.
For two, the initramfs script that mounts the rootfs needs go into a
waiting loop (0.5 sec intervals) for their devices (going on quic
Just checked that the same applies for encrypted non-rootfilesystems on
external disks, too. (/etc/init.d/cryptdisks*)
Since md and lvm devices are set up by udev, cryptdisks scripts need to
contain a waiting loop for their disks, or need to be called by udev
rules themselves.
--
encrypted root
Public bug reported:
Binary package hint: cryptsetup
ubuntu 8.04
md and lvm devices are set up by udev rules.
cryptsetup races the hotplug system and fails if they are not set up
instantly.
cryptsetup scripts in initramfs and /etc/init.d/ should go into a
waiting loop (0.5 sec intervals) for t
** Description changed:
Binary package hint: mdadm
(ubuntu 8.04)
- When --incremental is used to assemble array incrementally (as is envisioned
for udev hotplugging)
- --incremental --scan --run does not start anything.
+ The man page suggests that "mdadm -IRs" will start the arrays
Public bug reported:
Binary package hint: mdadm
Initramfs has to start (selected) md devices in degraded mode. (The ones that
contain the rootfs and swap/resume partition, if they didn't start after some
time of udev hotplugging.)
It seems to be preferable to use --incremental not only in the
The installer seems to work around the issue of an unset hostname in
initramfs by putting an ARRAY line into the mdadm.conf file, or by
having an unset hostname when creating the md device. Whichever, this
error does not appear after raid installations.
--
boot from raid1 root fails because of mi
--incremental is available in hardy (8.04)
Some info on howto enable it is available on:
https://wiki.ubuntu.com/BootDegradedRaid
--
udev not using mdadm incremental
https://bugs.launchpad.net/bugs/157981
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
** Summary changed:
- initramfs-tools script doesn't wait for device initialization, preventing
mdadm to assemble md arrays
+ mount script doesn't wait for root device initialization, preventing
udev+mdadm/cryptsetup to assemble md arrays
** Description changed:
script '/usr/share/initramfs-
** Summary changed:
- Segfault when readding removable devices
+ Segfault when readding hotplug devices
** Description changed:
Binary package hint: mdadm
- When an external drive with a raid 1 member (say /dev/sdc1) gets disconnected
and is subsequently re-added with "mdadm --add /dev
Public bug reported:
Binary package hint: mdadm
ubuntu 8.04
When "mdadm --incremental /dev/sdXY" is used to incremantaly assemble an
array (as udev is supposed to do instead of --assemble --scan), after a
reboot that cleared device nodes from prior --assemblies, mdadm fails
because of missing d
can not change this to wishlist / upstream
--
option to start selected arrays in "auto-read" mode (like --incremental)
https://bugs.launchpad.net/bugs/251646
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ub
Public bug reported:
ubuntu 8.04
Running on a degraded 2 device raid1 array with a single member. [2/1] [U_]
that holds lv_root and lv_swap.
It may be that the raid was not cleanly stopped prior to powerdown (as
the rc scripts don't do that), or that it was first restarted ok, or
being incremen
(Tested with two local replicas.)
--
rename files instead of deleting and copying again.
https://bugs.launchpad.net/bugs/253319
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
htt
Manual says:
xferbycopying: The default value istrue.
But the GUI does not seem to indicate that a renamed file will be copied:
(a: file /b: absent)
(a: deleted / b: u nchanged file)
--
rename files instead of deleting and copying again.
https://bugs.launchpad.net/bugs/253319
You received this b
Oh very good, the changelog sounds just like what I was thinking about.
Is this enabled by default?
--
rename files instead of deleting and copying again.
https://bugs.launchpad.net/bugs/253319
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
Thank you for checking the command line.
Well, this may then be a UI bug, now.
** Summary changed:
- rename files instead of deleting and copying again.
+ UI not showing xferbycopying feature (renaming instead of deleting and
retransfering)
** Description changed:
- Binary package hint: uniso
When a disk fails in a running system a raid will run degraded. The
System doesn't stop, and probably should't. The mdadm notification
functionality brings this to the admins attention.
So changing the default to bootdegraded=yes seems reasonable, once the
patches are tested to work with enough co
Thank you for the screenshots. The button order also seems reversed in
the subsequent windows to create new profiles. I noticed this because I
kept hitting cancel after entering the info.
--
OK buttons in profile wizard reversed
https://bugs.launchpad.net/bugs/253283
You received this bug notific
Alexey!
I'd like to say thank you.
For providing patches to the laptop-mode related things in ubuntu.
It was good to see your work apear.
--
acpi-support should let laptop-mode-tools run properly
https://bugs.launchpad.net/bugs/250938
You received this bug notification because you are a member o
Hi Tormod,
you asked:
3. Are some fixes needed in the pm-utils package as well?
Can you reference other bug reports (with patches)?
I do remeber two things, first Bug #239419 (pm-utils)
"pm-utils has laptop-tools script which conflicts with laptop-mode-tools"
has been wrongly set as a duplicat
Thank you for reassigning the bug.
Yes, the info should really be in the documentation, too.
I have filed this from practice. Many support requests deal with (new,
aka ex windows) users that have installed ubuntu not able to easily
collaborate with other users on their ubuntu installation.
The e
The wording of man pam_umask seems pretty much the same as what used to be in
login.defs before.
http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=10;filename=login.defs.diff;att=1;bug=282822
I have also made the experience that some graphical user managment tools
do not keep gids eqal to uids an
I agree, there are of course much more fine grained methods than the group of
all users. And to be honest when adminstering larger systems the users group is
probably not good for much more then giving all users write access to some
device, or to files that are served on the net. Now, it's not
Yes, I think you are right. Since the laptop-mode messing has fortunately been
removed from acpi-support the setting is obsoleted there and serves only for
confusion.
Alexey wrote:
It's interesting to know that current acpi-support in Debian unstable
(1.109-5) has this comment in /etc/default/
Thank you for your comments.
Then the current state I see in intrepid is this:
- You still need to "ENABLE_LAPTOP_MODE=1" in /etc/default/acpi-support
(Bug 244838)
- The /etc/laptop-mode/laptop-mode.conf default hdparm -B value has been
changed from 254 to 255.
This may be OK for consistency o
When resposibility is reestablished for /etc/laptop-mode/laptop-mode.conf the
ENABLE_LAPTOP_MODE_ON_BATTERY=yes default from debian's laptop-mode package
will and can enable laptop_mode when on batteries, no problem.
Package pm-utils has had a hacked laptop-tools script in hardy all the time
t
Hi,
https://wiki.ubuntu.com/PowerManagement has been updated to respect the fixes
for intrepid (ubuntu 8.10).
You currently still need to follow the steps mentioned there for hardy
(ubuntu 8.04) installs.
(I guess Vincenzo Ciancia who reported his issues where fixed with
recent hardy updates e
Dustin, you could have open a separate bug with your debconf patch to
track your work and at the same time keep the comunity updated and able
to give you feedback in a more organized manner.
> the default being BOOT_DEGRADED=false, which is the
conservative/traditional behavior.
Only some may con
Wow, Dustin we again wrote or comments almost simultaneously. Thank you for
separating the issue.
--
cannot boot raid1 with only one disk
https://bugs.launchpad.net/bugs/120375
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu
> the default being BOOT_DEGRADED=false, which is the
conservative/traditional behavior.
Only some may consider this "conservative" behaviour a broken behavior,
when a system on a "redundant array of independent disks" will degrade
just fine when running, but won't even come up when booting.
The
Public bug reported:
Binary package hint: mdadm
It is said that the intrepid fix to Bug #120375 added support to mdadm and
initramfs-tools for configurable booting degraded RAIDs, but a systems with
/home on a degraded array doesn't come up.
The particular array needs to be "mdadm --run /dev/
This issue has been separated out from Bug #120375 in order to track it
separately.
(Don't mark this as a duplicate, like 4 others before.)
--
home array not run when degraded on boot
https://bugs.launchpad.net/bugs/259145
You received this bug notification because you are a member of Ubuntu
Bug
I have separated out the issue of booting with degraded non-root arrays
into Bug# 259145.
As a user merely helping to gather info I can't say if updates to hardy
(ubuntu 8.04) will be made available. Dustin?
--
cannot boot raid1 with only one disk
https://bugs.launchpad.net/bugs/120375
You recei
Public bug reported:
Binary package hint: laptop-mode-tools
When the filesystem is on a raid device lm-profiler only reports only disk
access by a process called md0_raid1 (the md module).
Unfortunately this information does not help in identifying the
processes that actually causes the disk a
Yes, /etc/default/laptop_mode seems more sane as a second config file
for laptop-mode-tools.
As you mentioned in Bug #250935 we have to keep in mind that enabling
the laptop-mode-tools by default is in fact a necessary change to fix
the load cycling issue for example.
IMHO laptop-mode-tools needs
Alexey, you did good in making the patch acceptable. (And since you had
success, even better!)
So second step would be to flip the settings the right way.
hdparm -B254 needs to be reintroduced because bug #172282 has changed
that setting in the meantime.
(Yann who reported 254 did not work for h
Reopening.
hdparm -B value 254 needs to be reintroduced because the fix to bug
#250935 ([intrepid] laptop-mode-tools needs to change its default
settings to match acpi-support and add hooks for pm-utils) has migrated
the old 255 setting from acpi-support into laptop-mode-tools.
** Changed in: lap
The volume should not be mounted. Especially if "do nothing" is
selected.
** Also affects: gnome-volume-manager (Ubuntu)
Importance: Undecided
Status: New
--
digikam cannot download pictures due to gvfsd-gphoto2
https://bugs.launchpad.net/bugs/288470
You received this bug notification
> Once
> the situation is detected, it needs to be noted
Right, this is important especially in cases where segmentation has
happened unintentionally. That is why I wanted mdadm to fail on
conflicting changes without --force, not auto-sync and emit an event
(email, beep, notification, whatever con
Additional thoughts why updating metadata looks more limiting than
beneficial to me:
Unintentional (intermittent) failures of disks won't cause conflicting
changes but auto re-sync events to appear.
Segmenting an array into parts with conflicting changes requires
repeated boots with separate part
> Because they might change after a reboot?
> We *explicitly* support people doing that.
Dropping to a rescue shell is the support if a new raid set up with
another (rescue) system comes up degraded upon reboot. But I don't see
why supporting that should prevent a proper raid setup. One that will
I'm also fine with this postponed for after release, segmenting a
raid into concurrent hot-pluggable parts is a case, without correct
support now.
> hot-plugging order much more
> > arbitrary, and even less worth of committing to the meta-data.)
>
> If I plug in one disk and make some changes, t
> I also agree with Philip's assessment. When it hits, it is
> devastating, but it takes a very specific series of events to hit,
> and asking people to not upgrade as a result is too extreme.
I agree:
Re-attaching parts of an array that have been running degraded
separately and contain the same
Dustin, I don't think this has anything to do with the failure hooks in
this case. :) (Here it's mdadm that does not pick up on the conflict.)
--
array with conflicting changes is assembled with data corruption/silent loss
https://bugs.launchpad.net/bugs/557429
You received this bug notification
** Description changed:
- Using the latest beta-2 server ISO and following
- http://testcases.qa.ubuntu.com/Install/ServerRAID1
+ Re-attaching parts of an array that have been running degraded
+ separately and contain the same amount and conflicting
+ changes, results in the assembly of a corrupt
Phillip, first please explain where/why you think "flip-floping would occur
continiously", in such a way that makes it not enough to never assemble
a corrupt array and notify someone to take care to reconcile the
conflicting changes if desired.
Because this seems to be the reason you want to break
> >> If I plug in one disk and make some changes, then unplug it,
> >> plug in the other disk, and make some changes to it,
> >
> > What would be your use-case?
>
> I don't understand this question. The use case is described in the
> text you replied to.
Please explain why someone would do that
> [auto-removing]
> prevents you from continuing to flip flop which disk you are using
> after they have been forked, and thus making things worse.
And, this is a program thinking it knows better than the user, mdadm
--incremental should not do that. If you continue to do that after you
have been
> the minimum action required to fix the bug is to simply reject the
> second disk, updating its metadata in the process.
>
> > No, [updating metadata] really makes things worse! It prevents the
> > user/admin from managing arrays (parts in this case) by simply
> > plugging disks.
>
> No it does
** Also affects: ubuntu-release-notes
Importance: Undecided
Status: New
** Description changed:
Binary package hint: util-linux
+
+ When using luks on top of software raid devices, linux_raid_member
+ devices can get opened as luks instead of being assembled into md
+ devices.
+
+ -
Jools packages http://malus.exotica.org.uk/~buzz/mdadm can be considered
as patching this bug.
--
Please upgrade to 3.1.x for lucid
https://bugs.launchpad.net/bugs/495370
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs ma
** Tags added: patch
--
Please upgrade to 3.1.x for lucid
https://bugs.launchpad.net/bugs/495370
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/l
I can't tell if the metadata has been altered. Scott do the dd files
contain data that looks altered or irregular in any way?
--
breaking raid: root raid_member opened as luks
https://bugs.launchpad.net/bugs/531240
You received this bug notification because you are a member of Ubuntu
Bugs, which
Just installed lucid beta2-alternate with luks on raid in virtualbox.
Guess what, all turning down of this seems to be based on false speculations.
If I boot the CD again in rescue mode after the install
* It wants to open all md member devices as luks and asks for passphrases for
each member.
*
101 - 200 of 1101 matches
Mail list logo
