Excellent. Sanity check here: This also means that trusty is not
affected because the udev rules don't match.
I have /lib/udev/rules.d/40-hyperv-hotadd.rules:
# On Hyper-V Virtual Machines we want to add memory and cpus as soon as they
appear
ATTR{[dmi/id]sys_vendor}!="Microsoft Corporation", GO
@ddstreet I can replicate the issue in us-west-2. All i3.2xls using ext4
as the filesystem I'm testing on.
ami-4e98182e (precise) - doesn't recognize device
ami-17ac2c77 (trusty) - no error
ami-edf6758d (xenial) - I/O errors
ami-a49b1bc4 (yakkety) - I/O errors
--
You received this bug notificati
@ddstreet us-east-1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1668129
Title:
Amazon I3 Instance Buffer I/O error on dev nvme0n1
To manage notifications about this bug go to:
https://bugs.launch
I tested this on a few i3.2xlarge instances using bonnie++ and an ext4
mounted filesystem
ami-cc10c1da (precise) - does not recognize the ephemeral device
ami-822bfa94 (trusty) - does NOT appear to be affected
ami-1ac0120c (xenial) - is affected
ami-e600d1f0 (yakkety) - is affected
--
You receiv
The cp -a triggers the BUG when calling lsetxattr on the target.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1371367
Title:
NULL pointer deference in set_nfsv4_acl_one
To manage notifications abo
Public bug reported:
I can reliably reproduce an NFS BUG for set_nfsv4_acl_one by running `cp
-a`. Both client and server are running in AWS EC2. The server mount is
on EBS. This error is new since upgrading our nfs server from natty to
precise.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Packa
