On 23.05.2015 03:12, Francis Gerund wrote:
> Am I correct to assume that this would ONLY affect systems that include a
> RAID-0 filesystem, and that it would not affect other ext4 systems using
> SSDs with "discard" in /etc/fstab?
It affects all file systems when used with discard on a raid0 devic
On 05/23/2015 02:55 AM, Florian Pritz wrote:
On 23.05.2015 03:12, Francis Gerund wrote:
Am I correct to assume that this would ONLY affect systems that include a
RAID-0 filesystem, and that it would not affect other ext4 systems using
SSDs with "discard" in /etc/fstab?
It affects all file syst
it says to run fsck
On Sat, May 23, 2015 at 11:16 AM, David C. Rankin <
drankina...@suddenlinkmail.com> wrote:
> On 05/23/2015 02:55 AM, Florian Pritz wrote:
>
>> On 23.05.2015 03:12, Francis Gerund wrote:
>>
>>> Am I correct to assume that this would ONLY affect systems that include a
>>> RA
On Sat, May 23, 2015 at 04:16:59AM -0500, David C. Rankin wrote:
> UUgh, dumb question, but... I have not used/configured this "discard", but I
> do have 6 Raid0 arrays spinning on my Arch server. Does this corruption
> potentially apply to me? Is this "discard" something that would be enabled
> by
arch-general-requ...@archlinux.org schreef op 2015-05-19 14:00:
Anyone have a system they haven't upgraded in ~24hrs to give it a
further test, see if logins are broken after the pam upgrade?
-te
I've had similar issues, except it broke systemctl --user functionality.
systemctl daemon-reexec
Sat, 23 May 2015 13:39:00 +0200
Alad Wenter :
> arch-general-requ...@archlinux.org schreef op 2015-05-19 14:00:
>
> > Anyone have a system they haven't upgraded in ~24hrs to give it a
> > further test, see if logins are broken after the pam upgrade?
> >
> > -te
>
> I've had similar issues, exce
Sat, 23 May 2015 13:39:00 +0200
This isn't about downgrading or rebuilding, but rather about sub-par
information. If you're upgrading a bunch of packages (your usual -Syu)
with 'pam' being one of many and it's not echoing any hint or warning
about a soname change, well, duh. PAM is such an essen
On Sat, May 23, 2015 at 6:59 AM, Jens Adam wrote:
>
> information. If you're upgrading a bunch of packages (your usual -Syu)
> with 'pam' being one of many and it's not echoing any hint or warning
> about a soname change, well, duh. PAM is such an essential library
...coupled with the fact I work
8 matches
Mail list logo