Public bug reported:
pam_umask.so is now included in libpam-modules.
** Affects: pam-umask (Ubuntu)
Importance: Undecided
Status: New
--
remove obsolete package pam-umask from repository
https://bugs.launchpad.net/bugs/253213
You received this bug notification because you are a
initramfs/scripts/local in 8.04 does have a timeout loop for the root
device.
The remaining mdadm bug numbers are listed on
https://wiki.ubuntu.com/BootDegradedRaid
** Changed in: initramfs-tools
Status: New = Fix Released
--
mount script doesn't poll if root device has been
Don't forget to update-initramfs -k all -u with the new udev rule
before rebooting, though.
--
--incremental not creating device nodes
https://bugs.launchpad.net/bugs/251663
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Hello Steve,
thank you for improving ubuntu.
The example came from the pam_umask man page, maybe I had some typo.
There is some history why this bug should be fixed. It is a regression that is
now easy to fix.
Before pam was introduced login provided the central point to set the UMASK
value
FYI here is a summary of a Sep 2005 discussion in debian, by now it may be
added that, as pam_umask supports the usergroups feature, it is no longer
neccessary to set the umask to 002 for all users, with pam_umask's usergroups
feature it will check if users are in a private primary user group.
Actually, libpam-modules are installed by default and this new
pam_umask.so should be enabled in common-session by default (Bug
#253096).
pam_umask now recovers the umask functionality that login once had for
pam systems. (see man pam_umask) It gets the users umask from several
places.
That
See Bug #253096 for the current state of umask setting.
--
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 Ubuntu.
--
ubuntu-bugs mailing
See Bug #253096 for the current state of umask setting.
--
/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 subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Hello Steve,
yes, it may be that the adduser maintainer could change his package,
adding redundant group configuration to all users. But other than that,
some GUI tools don't seem to always rely on adduser (configuration) or
even (debian) policy for user and group ids, unfortunately. (It's
Public bug reported:
Binary package hint: unison
Within the graphical profile wizard the right button aborts and the left button
is OK.
** Affects: unison (Ubuntu)
Importance: Undecided
Status: New
--
OK buttons in profile wizard reversed
https://bugs.launchpad.net/bugs/253283
Public bug reported:
Binary package hint: kdebase
To reproduce configure a domain that provides service discovery information in
kcontrolcenter / zeroconf.
For example dns-sd.org.
Then you will be able to browse their published services under Network
shortcut in KDE.
But when following the
This is ubuntu 8.04 (hardy)
--
Links retrieved over dns-sd (service discovery) not working
https://bugs.launchpad.net/bugs/253282
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
Public bug reported:
Binary package hint: unison
When files gets renamed in replica A, unison shows that the original file is
getting deleted in replica B and the renamed file is copied again.
This is particulary unfortunate with picture archives, as they get more
often renamed but less often
Sorry prior post was ment for another bug, the race condition with
degraded raids in this bug has different behaviour mentioned in
aformentioned kernle list archive.
--
udev not using mdadm incremental
https://bugs.launchpad.net/bugs/157981
You received this bug notification because you are a
When this occurs the drives are accessed continously, system hangs.
--
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 subscribed to Ubuntu.
--
ubuntu-bugs mailing list
When this bug occurs the drives are accessed continously, system hangs.
--
-ARs fails with prior --no-degraded assemblies
https://bugs.launchpad.net/bugs/244792
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
4 of the 5 bugs taged as duplicates use a separate home array,
the fix will not let such systems boot degraded.
WARNING:
The mdadm - 2.6.7-3ubuntu2fix uses mdadm --assemble --scan on a system based
on udev hotplugging.
It will start all partly attatched arrays in degraded mode.
When any
Well, the issue filed here, is
autocreated mdadm.conf prevents autodetection of cold- and hotplugging.
I found out not only the ARRAY lines, but also the homehost prevents
autotection of arrays.
The homehost feature may have been good to prevent systems with global
mdadm --assemble --scan
Just checked that the same applies for encrypted non-rootfilesystems,
too. (/etc/init.d/cryptdisks*) If for example external disks are slow
crypdisk fails.
Since md and lvm devices are set up by udev: init.d/cryptdisk-early and
cryptdisks (or just cryptdisk.functions) need to contain a timeout
4 of the 5 bugs taged as duplicates use a separate home array,
the fix will not let such systems boot degraded.
WARNING:
The mdadm - 2.6.7-3ubuntu2fix uses mdadm --assemble --scan on a system based
on udev hotplugging.
It will start all partly attatched arrays in degraded mode.
When any
To reproduce change /etc/udev/rules.d/85-mdadm* to do mdadm
--incremental /dev/%k and reboot.
After initramfs drops you to a console try mdadm --incremental manually.
--
--incremental not creating device nodes
https://bugs.launchpad.net/bugs/251663
You received this bug notification because you
You can make your fat filesystem permissions look like matching to your default
umask.
Mount options:
for umask 002: dmask=002,fmask=113
for umask 022: dmask=022,fmask=133
(do not use the unspecific umask option)
As a workaround adjust your personal hal vfat mount options in the
More information on a corresponging debian bug, that has been closed by
maintainers without resolving.
http://bugs.debian.org/344278
--
can't easily use unison-gtk to sync a local folder to my VFAT USB drive
https://bugs.launchpad.net/bugs/118283
You received this bug notification because you
You can make your fat filesystem permissions look like matching to your
default umask.
Mount options:
for umask 002: dmask=002,fmask=113
for umask 022: dmask=022,fmask=133
(do not use the unspecific umask option)
As a workaround adjust your personal hal vfat mount options in the
gconf-editor,
More info in Bug #252351
--
The default umask should be set to 077. XDG_PUBLICSHARE_DIR should have umask
022
https://bugs.launchpad.net/bugs/204577
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
It's ment to inform the user during install and GPL of course.
--
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
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Oh, the problem with the current state is that umask is set all over the
place in shell config files, xsessions, and do not work for ssh logins
for example.
--
pam_umask.so missing in common-session
https://bugs.launchpad.net/bugs/253096
You received this bug notification because you are a
Public bug reported:
pam_umask.so determines the umask (from system and user config files (see man
page)) and sets it accordingly.
The umask should not be set in common-session because it would override
all user specific configs, but the option usergroups is neccessary to
let it check if
Public bug reported:
Ubuntu uses private user groups.
In order for the users to belong be added to the users group by default
/etc/security/groups needs to contain a line like this one:
*; *; *; Al-2400; users
(Context is also Bug #252351)
** Affects: pam (Ubuntu)
I just noticed that with slowly-appearing drives (with md devices on it) the md
device will not exist on the regular run of init-premount/mdadm. But since
introducing another waiting loop into the coldplug driven boot does not make
much sence it'll be preferable to just do degration with
I just noticed that with slowly-appearing drives (with md devices on it) the md
device will not exist on the regular run of init-premount/mdadm. But since
introducing another waiting loop into the coldplug driven boot does not make
much sence it'll be preferable to just do degration with
Ah, packages server is back up.
I see the whole rootdelay loop has been copied from the local script and
also the dropping to the console when ${cryptsource} is missing.
But the recent local script will execute additional failure hooks. For
example degraded arrays will only get started by
Public bug reported:
Binary package hint: grub
(I don't know if this is grub or grub-installer)
It would be nice if grub-install could default to always setup the boot
sector of the / or /boot partition to be chainloadable also (as a
backup).
* Recovering from an overwritten MBR would be as
Hi, concerning the boot process you can test the current patches
https://wiki.ubuntu.com/BootDegradedRaid
for Bug #120375
--
Mdadm segfault on booting Hardy
https://bugs.launchpad.net/bugs/252485
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I think it can be understood that using mdadm --assemble --scan instead of
doing selective mdadm --run device calls on all devices ${ROOT} depends on
could be a reasonable and quick fix, if the information is not available
somwhere allready. Full support here.
My interest lies in getting the
I think it can be understood that using mdadm --assemble --scan instead of
doing selective mdadm --run device calls on all devices ${ROOT} depends on
could be a reasonable and quick fix, if the information is not available
somwhere allready. Full support here.
My interest lies in getting the
Ok, a timeout loop looking for (slower) source devices sounds just what
I was missing / suffering from in hardy. I whish there were a webcvs or
somthing, would make it easier to compare/check, maybe there is and I
don't know. http://packages.ubuntu.com seems unavailable.
You may change status if
clearer when staring degraded raids stays the resposibility of startup
scripts.
Or the user manually starting an array. (possibly by right clicking)
Then, when two array disks are pluged in and it doesn't come up it is
always clear they the array is not complete.
--
inconsistency with the
Public bug reported:
Binary package hint: hdparm
Mention that (in debian and ubuntu) hdparm settings may be set by a script
startup script or when a device is plugged in by udev rules.
And that some packages like laptop-mode-tools can take care of setting some
hdparm parameters dynamicly
Public bug reported:
Binary package hint: thunar
If there are two partiontions thunar will umount both if one is
unmounted. This is good because it makes unpluging save.
With one partition mounted through fstab though the error message does
not relate to the partition that one tried to unmount.
Public bug reported:
Binary package hint: debian-installer
On systems that are set up statically mdadm.conf is often used to list
the md devices that should be set up and the startup script just calls
mdadm --assemble --scan.
But on systems oriented towards hotplug ability this prevents arrays
Public bug reported:
Binary package hint: debian-installer
Following is a little informative text for the set up users and
passwords stage:
---
It is easy for multiple users to collaborate on a debian/ubuntu system.
Just keep in mind that access to files always depends on the permissions
of
Thank you for your comments and I'm sorry me slowly commenting overlapped with
your updated patches. (Of course you just worked to fast ;-), and fixed things
beforehand, perfect. :)
It's good to see that happen, and I've seen the merrit of the while loop
in intrepid now. It looks much better
Thank you for your comments and I'm sorry me slowly commenting overlapped with
your updated patches. (Of course you just worked to fast ;-), and fixed things
beforehand, perfect. :)
It's good to see that happen, and I've seen the merrit of the while loop
in intrepid now. It looks much better
Hallo Reinhard,
are you refering to udev settling?
One of my usb disks is so slow in initializing, that it won't even trigger an
udev event until 8 seconds after udev has been started in initramfs.
Is the intrepid initramfs-tools/scripts/local-top/cryptroot viewable
somewhere on the web?
--
Hi, some feedback about the patches.
Does it matter if call_failure_hooks is allways called?
mdadm --run --scan will start all arrays degraded not only the one needed for
the rootfs (and its lvm and crypt respectively).
It will start for example a partial array from a removable disk that was
After
# We've given up,
A while loop is calling panic. An if statement might look better.
--
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
Server Team, which is a subscriber of a duplicate bug.
I also noticed that mdadm -E also reported the member device flaged as
write-mostly, even though I have never set this.
It may have been the installer because it was on a usb drive, I tested
on a new install but have not seen that.
So it may have been set during suspend/resume or have been
Public bug reported:
ubuntu 8.04 (2.6.24-19)
When mounting an ext3 fs with -t ext2 (to stop the constant journal
updates even no data is written or read), or when setting the mount
option in fstab, the kernel does not honor this.
The mount command lists the mount as ext2 but the filesystem is
Using --incremental (Bug #157981) avoids this bug with ubuntu udev
hotplugging.
--
-ARs fails with prior --no-degraded assemblies
https://bugs.launchpad.net/bugs/244792
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
/usr/share/initramfs-tools/scripts/local in 8.04 contains a checking
loop.
** Changed in: initramfs-tools (Ubuntu)
Status: Confirmed = Fix Released
--
mount script doesn't poll if root device has been initialized, preventing
udev+mdadm/lvm/cryptsetup to do its job
Hi, some feedback about the patches.
Does it matter if call_failure_hooks is allways called?
mdadm --run --scan will start all arrays degraded not only the one needed for
the rootfs (and its lvm and crypt respectively).
It will start for example a partial array from a removable disk that was
After
# We've given up,
A while loop is calling panic. An if statement might look better.
--
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-bugs
This applies to both initramfs and init.d scripts.
(root and home raids with devices on external disks take longer)
sleep 0.1 seconds intervalls are probably ok
** Summary changed:
- crypdisk setup does not wait properly for its devices to appear
+ crypdisk setup does not wait properly for its
** 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 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
--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
** 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
** 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
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
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
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
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
** 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
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
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
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
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
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
*** 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
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
*** 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
** 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
+
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
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
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
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
** 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
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
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
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
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
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
This bug report is inteded to document the adaption of laptop-mode-
tools.
Wouldn't the patch to pm-tools be the matter of a pm-tools bugreport?
Though this bugreports may be linked with current pm-tools package
interfering with package laptop-mode-tools, I do think this bug needs to
be separate
I added notes on how to adjust the ubuntu hotplug setup to cope with raid
devices at:
https://wiki.ubuntu.com/BootDegradedRaid
See under Implementation.
--
cannot boot raid1 with only one disk
https://bugs.launchpad.net/bugs/120375
You received this bug notification because you are a member
Public bug reported:
Binary package hint: mdadm
(8.04)
mdadm --assemble --scan --no-degraded creates inactive arrays that
will not start with a subsequent mdadm --assemble --scan (--run)
(N.B. that is what the the udev rules and boot scripts are trying to do
instead of using --incremental)
(The array will be crated inactive only if degraded of course)
--
-ARs fails with prior --no-degraded assemblies
https://bugs.launchpad.net/bugs/244792
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Public bug reported:
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/md0 /dev/sdd1 mdadm quits
with segmentation fault.
The udev rules supplied for mdadm should trigger a mdadm --fail
Public bug reported:
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.
mdadm --incremental --scan --run does not start the arrays that have
been
Public bug reported:
Binary package hint: mdadm
There is inconsistency in the --no-degraded and --incremental option.
They will start degraded arrays, if they have been --run degraded
before.
Its clearer to report problems and and do interventions when staring degraded
raids stays the
I added notes on how to adjust the ubuntu hotplug setup to cope with raid
devices at:
https://wiki.ubuntu.com/BootDegradedRaid
See under Implementation.
--
cannot boot raid1 with only one disk
https://bugs.launchpad.net/bugs/120375
You received this bug notification because you are a member
Public bug reported:
Binary package hint: acpi-support
The different power management packages in ubuntu are patched.
Where ist the documentation about the design reasoning and configuration
decisions.
Obviously part of the policy is that CPU frequency and powersettings are
controlled by
1001 - 1100 of 1115 matches
Mail list logo
