Not sure how the truncate tool works internally, but it does the same
with the -s parameter.
$ truncate -s 48T size-test
truncate: failed to truncate 'size-test' at 52776558133248 bytes: File too large
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Well ... the tool could print all possible reasons of the failure to
avoid confusion. Writing one byte at the last position seems to me a
good solution. If that's acceptable, it would really improve the user
experience. Thank you.
--
You received this bug notification because you are a member of
Oh, sorry, I thought the limit cannot be reached that easy in case of
sparse files full of unalocated blocks. Apparently the limit includes
the unallocated space.
I retested that again and the sparse file really gets truncated to 16TB
and I believe that's exactly the moment when the tool should
Public bug reported:
It seems e2image is unable to work correctly with large filesystems. I
get the following error with etx4 on top of 48TB RAID5 array.
# e2image -pr /dev/md3 md3.e2i
e2image 1.46.5 (30-Dec-2021)
Scanning inodes...
Copying 802818 / 1547571 blocks (52%) 00:02:21 remaining at
Public bug reported:
I was curious how e4defrag works and how it could optimize a speed and
loudness of 48TB mdraid array with four 16TB drives in RAID5 and tried
the defrag on the whole mountpoint. After a couple of minutes the
mountpoint became inaccessible and I found two of the drives marked
I started some investigation with the pulseaudio upstream and the issue
is caused by the fact only the currently selected profile receives
updates of the the plugged/available state since PA13 and that conflicts
with the feature of switching the unavailable profiles away. They never
get back from
Hello. Like mentioned in #1905078, I don't have the apport package
installed and don't plan to do so due to various reasons. Right now I'm
working with PA downgraded from 1:13.99.1-1ubuntu3.7 to
1:11.1-1ubuntu7.10 that doesn't exhibit such problems.
--
You received this bug notification because
Hi. Sorry, I understand you have a process, but ... the ubuntu-bug tool
is broken/annoying/collecting info that I don't wanna disclose and I
always uninstall apport. Moreover, I've already downgraded all relevant
PA packages from 1:13.99.1-1ubuntu3.7 to 1:11.1-1ubuntu7.10, since the
second bug
I had a talk with the upstream on #pulseaudio IRC channel and the issue
has not been resolved upstream yet. The guys expect the fix before the
PA 14 release.
** Bug watch added: gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues #1032
Upstream report:
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1032
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1905080
Title:
After upgrading from
It seems the fix went to 13.99.2 and the Ubuntu 20.04 version is
13.99.1.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1905078
Title:
pavucontrol duplex profiles
I just received some tip on the #pulseaudio IRC channel ...
The above bug has been fixed with the following merge requesrt:
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/349
Could you please patch/upgrade the package?
--
You received this bug notification because you
I just studied the PulseAudio 13 release notes and it is probably
related to the following "improvement" ...
::Automatically switch away from unavailable card profiles::
How about restoring the profile when it becomes available again?
--
You received this bug notification because you are a
** Also affects: pulseaudio (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: systemd (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
** Also affects: pulseaudio (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: systemd (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
Public bug reported:
Before the upgrade the HDMI 4 digital stereo output was chosen
automatically for my nvidia GF card and was usable by the players
immediately after turning the TV on. After the upgrade I have to switch
the profile from Disabled to HDMI4 each time I turn the TV on. It
doesn't
Public bug reported:
I just upgraded from Ubuntu 18 to 20 and analog stereo duplex profile is
gone. The duplex profile was there and was working properly before.
The following seems to be related:
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/750
** Affects: systemd (Ubuntu)
17 matches
Mail list logo
