I created a Fedora Workstation issue to track the progress, and figure
out if any or all of the desktops want to do full preemption by
default.
https://pagure.io/fedora-workstation/issue/228
___
devel mailing list -- devel@lists.fedoraproject.org
To
terion will be regarded as a "conditional blocker" (as
> described in
> https://fedoraproject.org/wiki/Blocker_Bug_FAQ#What_about_hardware_and_local_configuration_dependent_issues.3F)."
Ack.
--
Chris Murphy
___
test mailing lis
u can use a newer
kernel that doesn't have the bug.
Or like Dusty suggests, give the Fedora 34 Cloud images a whirl. Out tomorrow!
--
Chris Murphy
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@list
efault in 5.12 kernel for desktop
> variants. With 5.12 it is possible for user to change it without efforts if
> they need this.
>
I see CONFIG_HAVE_PREEMPT_DYNAMIC=y with kernel
5.12.0-0.rc8.191.fc35.x86_64+debug.
--
Chris Murphy
___
devel mailin
On Sun, Apr 25, 2021, 10:36 AM Michael Hennebry <
henne...@web.cs.ndsu.nodak.edu> wrote:
> On Sat, 24 Apr 2021, Chris Murphy wrote:
>
> > You need to use -B to bind mount the pseudo filesystems, and probably
> also
> > need to include /sys
>
> > grub2-install
ably also
> need to include /sys
>
>
> grub2-install /dev/sda3
> grub2-mkconfig > /boot/grub2/grub.cfg
> exit # out of chroot?
>
> reboot
>
> Should work?
grub2-install /dev/sda
--
Chris Murphy
___
users maili
to create partitions automatically. Install.
Two independent backups for anything important.
--
Chris Murphy
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Cond
l: journalctl -b > /path/to/rw/mount/journal.log
And then post the journal.log and /etc/fstab somewhere.
--
Chris Murphy
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fed
mkconfig -o /boot/grub2/grub.cfg
> The UUID not found is used by the F33 live DVD.
> Changing sda3's UUID to that seems a bad idea.
It is. You should use 'sudo blkid' and find out what UUID is on sda3
and put that into fstab for /
--
Chris Murphy
command is used for a live install.
08:18:29,672 INF program: Running... rsync -pogAXtlHrDx --exclude
/dev/ --exclude /proc/ --exclude /tmp/* --exclude /sys/ --exclude
/run/ --exclude /boot/*rescue* --exclude /boot/loader/ --exclude
/boot/efi/loader/ --exclude /etc/machine-id /run/install/source
h this
write pattern, it's already unsharing any shared extents from
snapshots or reflinks. Since the whole file isn't (re)defragmented
every time autodefrag is triggered by the write pattern, it's not
going to add much (if at all) to unsharing extents.
--
ompose test cases to release
> criterion? Or the inverse? Something like "Failures of test case foo,
> bar, and baz may constitute a violation of release criterion qux"?
I'm pretty sure it's all contained to the Basic, Beta, and Final
release criteria pages.
--
Chris Murphy
_
t;> https://pagure.io/fedora-infrastructure
>
> ___
> test mailing list -- test@lists.fedoraproject.org
> To unsubscribe send an email to test-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.o
he intent of bootupd.
https://github.com/coreos/bootupd/
And also include 'grub2-install' on BIOS systems to ensure the
embedded instance is also kept up to date. And a possible future
feature is EFI system partition syncing in the case of multiple ESPs.
--
Chris Murphy
__
case ... it works!
Please report your test results here ->
https://testdays.fedoraproject.org/events/111
BIOS firmware and additional architectures are covered in the test
day, see the page for details.
--
Chris Murphy
___
devel mailing list -- de
ithub.com/systemd/systemd/issues/17756), which
> still is not working, because of the two issues mentioned there (and less
> systemd-boot upstream interest as it seems).
That is unfortunate.
--
Chris Murphy
___
devel mailing lis
On Sat, Apr 10, 2021 at 7:35 PM Neal Gompa wrote:
>
> On Sat, Apr 10, 2021 at 9:20 PM Chris Murphy wrote:
>
> > "$BOOT must be a file system readable by the firmware"
> >
> > That condition is met by efifs, ergo by wrapping GRUB file system
> > modul
do file /boot/grub2/grubenv
> /boot/grub2/grubenv: symbolic link to ../efi/EFI/fedora/grubenv
grubenv and grub.cfg are no longer on the ESP, starting with Fedora
34. Both are located in /boot/grub2/ as a result of:
https://fedoraproject.org/wiki/Changes/UnifyGrubConfig
--
Chris Murphy
_
On Sat, Apr 10, 2021 at 3:10 PM Vitaly Zaitsev via devel
wrote:
>
> On 10.04.2021 23:00, Chris Murphy wrote:
> > Both of those resolve to $BOOT/loader/entries and systemd-boot
> > supports either EFI System partition or Extended Boot Loader
> > partition.
T32, it's the firmware that reads it.
And efifs means the firmware can read anything we want it to read.
https://github.com/pbatard/efifs
--
Chris Murphy
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@li
man pages, my working assumption is all Max limits
are in effect. If any Max value is busted, vacuuming is triggered. If
anyone knows differently, now would be a good time to know!
--
Chris Murphy
___
devel mailing list -- devel@lists.fedorap
On Mon, Apr 5, 2021 at 12:12 PM Richard Shaw wrote:
>
> On Mon, Apr 5, 2021 at 11:43 AM Chris Murphy wrote:
>>
>>
>>
>> On Mon, Apr 5, 2021, 6:28 AM Richard Shaw wrote:
>>>
>>> On Sun, Apr 4, 2021 at 5:19 PM Chris Murphy wrote:
>>>
On Mon, Apr 5, 2021, 6:28 AM Richard Shaw wrote:
> On Sun, Apr 4, 2021 at 5:19 PM Chris Murphy
> wrote:
>
>> On Sun, Apr 4, 2021 at 5:40 AM Richard Shaw wrote:
>>
>> > It should be possible, however, to mark the images folder +C even if it
>
On Sun, Apr 4, 2021 at 5:40 AM Richard Shaw wrote:
>
> On Sat, Apr 3, 2021 at 11:40 PM Chris Murphy wrote:
>>
>> On Sat, Apr 3, 2021 at 10:42 AM Richard Shaw wrote:
>> >
>> > Before I submit a BZ I figured maybe some discussion was in order.
>> >
ter then that maybe could become the default for
Windows guests. I don't expect unsafe could ever be a default.
https://documentation.suse.com/sles/11-SP4/html/SLES-kvm4zseries/cha-qemu-cachemodes.html
--
Chris Murphy
___
users mailing list -
irectory isn't yet nodatacow.
--
Chris Murphy
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduc
On Fri, Apr 2, 2021 at 4:23 AM Patrick O'Callaghan
wrote:
>
> On Thu, 2021-04-01 at 23:52 -0600, Chris Murphy wrote:
> > It's not an SMR concern, it's making sure the drive gives up on
> > errors
> > faster than the kernel tries to reset due to what it think
ers need to reflect the specs, and then
there's installer and image builder work.
This particular bug might have a simple fix, but you'd need to help
the upstream projects find out exactly what's wrong.
--
Chris Murphy
___
test mailing list -- test@lists
boot on a Btrfs subvolume which is how the
installer lays out all Btrfs setups.
--
Chris Murphy
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fe
On Thu, Apr 1, 2021 at 5:53 AM Patrick O'Callaghan
wrote:
>
> On Wed, 2021-03-31 at 18:00 -0600, Chris Murphy wrote:
> > Nothing to add but the usual caveats:
> > https://raid.wiki.kernel.org/index.php/Timeout_Mismatch
>
> That´s pretty scary, though the drives I´m using a
st usage without getting too caught
> up in all of the possible hardware combinations, especially since one
> major video card manufacturer isn't the best at supporting Linux.
>
I agree.
--
Chris Murphy
___
test mailing list -- test@lists.fed
systems of this size.
--
Chris Murphy
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
L
I'm writing can be compressed
50%, and the device maxes out at 35 M/s writes, in effect I get 70 M/s
writes. Latency per IO is still the same, but again less writes means
less IO competition so there's still some gain even on the latency
front.
--
Chris Murphy
_
g multiple snapshots. It'll tell you about all of the
instances of the files sharing that one bad block.
--
Chris Murphy
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code
it should just skip those (with some noise) and
continue on. If not then I've got an idea for a work around.
--
Chris Murphy
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraprojec
gt; to the end of the command (ie / in my case). It would help people like me
> from getting confused and hopefully bring in more casual tinkerers trying the
> new change out.
>
> Thanks.
Thanks for the feedback, I've updated that section.
--
Chris Murphy
__
that were
stable already in the hours before beta freeze actually didn't make it
onto beta composes.
--
Chris Murphy
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code o
f it taking hours for a 40T
file system, because the whole tree must be created and written before
the mount can complete. For me on a full 1T file system it took
*maybe* 1 minute.)
--
Chris Murphy
___
users mailing list -- users@lists.fedoraproj
early bootstrapping sequence before we even usually see
anything.
--
Chris Murphy
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fe
D is it goes read-only. Not the file system, the drive - and this
too is totally silent in my handful of experiences with this failure
mode, happily accepts all write command without error but none of them
are persistent. Another mode of SSD failure that's common is, it just
vanishes off the bus. D
of any kind is not normal, the
source should be found. Persistent stats are also retained in the file
system metadata, retrievable by:
btrfs device stats /mntpoint or /dev/ node(s)
--
Chris Murphy
___
users mailing list -- users@lists.fedoraproject.org
To unsu
and work to find the trends and then
publish it and maintain it.
--
Chris Murphy
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en
./15/./22 -n
standby,250
Since it's unmounted, fatrace won't work, but blktrace will..
blktrace -d /dev/sdb -o - | blkparse -i -
It will generate a lot of lines but it'll also report the process
that's sending commands to the drive.
--
Chris Murphy
___
stupidly doing too many fsync:
>system-nspawn --system-call-filter='~sync:0 fsync:0'
That is awesome! Way easier to deal with than eatmydata.
--
Chris Murphy
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email
On Thu, Mar 25, 2021 at 7:26 PM Chris Murphy wrote:
>
> The problem is well understood for some time.
> https://lwn.net/Articles/572911/
This is an update on that 8 year old story. Last year writebehind
patches were proposed, and a discussion ensued.
https://lore.kernel.org/linu
. Try:
$ sudo modprobe xfs
Now try mount. Does that work?
--
Chris Murphy
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org
I'm using the copr build in f34. It seems to be working but the ipv6
ipv4 flip on successive runs as if there's some kind of race in
reporting one or the other first? Is that relevant?
[chris@fmac ~]$ resolvectl query google.com
google.com: 2607:f8b0:400f:805::200e -- link: enp2s0f0
On Thu, Mar 25, 2021 at 7:26 PM Chris Murphy wrote:
>
> The defaults are crazy.
> https://lwn.net/Articles/572921/
>
> Does this really make a difference though outside the slow USB stick
> example? I don't know. Seems like it won't for fsync heavy handedness
> because th
On Thu, Mar 25, 2021 at 6:39 AM Richard Shaw wrote:
>
> On Wed, Mar 24, 2021 at 11:05 PM Chris Murphy wrote:
>> Append writes are the same on overwriting and cow file systems. You
>> might get slightly higher iowait because datacow means datasum which
>> means more metad
0 but double check that, there's w and W and one of them
controls write cache, the other is dangerous.
$ cat /etc/udev/rules.d/69-hdparm.rules
ACTION=="add", SUBSYSTEM=="block", \
KERNEL=="sd*[!0-9]", \
ENV{ID_SERIAL_SHORT}=="WDZ47F0A&quo
On Thu, Mar 25, 2021 at 8:59 AM Roberto Ragusa wrote:
>
> On 3/25/21 4:25 AM, Chris Murphy wrote:
>
> > It might be appropriate to set dirty_bytes to 500M across the board,
> > desktop and server. And dirty_background to 1/4 that. But all of these
> > are kinda rudimen
l the drives and
disable the write cache. It isn't worth the trouble.
--
Chris Murphy
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs
how this.
> However, I let a rebalance run overnight.
It shouldn't be necessary to run balance. If you've hit ENOSPC, it's a
bug and needs to be reported. And a separate thread can be started on
balance if folks want more info on balance, maintenance, ENOSPC
things. I don't ever worry about
or generally not useful (i.e. either bad or ambiguous) to change it.
--
Chris Murphy
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedorap
les to that bug, and everything else can just go in the description.
Also note any other customizations to /proc or /sys that differ from
Fedora defaults.
--
Chris Murphy
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to
The bug report:
https://bugzilla.redhat.com/show_bug.cgi?id=1941335
Fix is nearly ready:
https://github.com/systemd/systemd/pull/19075
--
Chris Murphy
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le
On Sun, Mar 21, 2021 at 4:37 PM Patrick O'Callaghan
wrote:
>
> On Mon, 2021-03-22 at 06:12 +0800, Ed Greshko wrote:
> > On 22/03/2021 02:27, Chris Murphy wrote:
> > > Some folks are reporting a hang when booting Fedora 33 this morning
> > > (or also possibly wake fr
dar=Sun *-*-* 01:00:00
The switch from GMT->IST and GMT->BST happen on 2021-03-28 01:00:00
Conversely in most of Europe, it will change 2021-03-28 but with two
differences that might be relevant: 02:00:00, and from Standard to
Daylight time.
--
Chris Murphy
_
with
md raid setups might want to set a reminder to enable the timer again
once the issue is sorted out.
--
Chris Murphy
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code
teroperability is a distinct weak point. Boot
Loader Spec is intended to address this, and is implemented in
Fedora's GRUB by the blscfg module, but isn't upstreamed yet. There's
still some work to do but we're pretty close to at least multiple
Fedora's sharing a single bootloader instance and /boot vol
On Mon, Mar 15, 2021, 11:16 PM David wrote:
> I seem to have lots of duplicate packages with the same name: one being
> F34 and the other F35.
>
autoremove and offline-distrosync will fix it.
> cat says I am on version 34,
>
> I want to get rid of any unnecessary 34 stuff and proceed to
ed
release or a stable release.
https://fedoraproject.org/wiki/Releases/Rawhide#Upgrade_from_existing_stable_install
> I think my first problem was that I was trying to import the key using sudo
> and not as root.
It should be the same.
--
Chris Murphy
__
generally if the system reboots and gets to a functioning desktop, any
smaller issues can be dealt with there.
--
Chris Murphy
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora C
ding internal read/write errors that don't always get reported to
the kernel, as well as UDMA errors, which are common with
connector+cable issues.
--
Chris Murphy
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test
/
sqlite3 history.sqlite 'VACUUM;'
That cleans the database. It will delete the other two files which
will reappear later once dnf starts writing to this database again.
--
Chris Murphy
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send
: started on
> devid 1
> Mar 13 17:34:39 fc35 kernel: BTRFS info (device sda5): scrub: finished on
> devid 1 with status: 0
That is strange. The scrub should find the same corruption. If you do:
ls -li /var/lib/dnf/history.sqlite
Is the reported inode number on the left 2239235?
Wha
They come and go in kernel rc development. Pretty
sure that particular lock dep warning was fixed a while ago. The
current Fedora kernel is 5.11.5 with 5.11.6 heading to stable soon, so
you should update.
--
Chris Murphy
___
test mailing list -- tes
or
> History database is not writable: SQLite error on
> "/var/lib/dnf/history.sqlite": Executing an SQL statement failed: disk I/O
> error
> Error: SQLite error on "/var/lib/dnf/history.sqlite": Executing an SQL
> statement failed: disk I/O error
> rc=1
Question
intage Dell PowerEdge that does
> not support booting from thumb drives.
Hmm, I've got a vintage 2006 Dell laptop that boots from a USB stick.
There might have been a BIOS setting to enable it.
--
Chris Murphy
___
users mailing list -- users
/show_bug.cgi?id=1933520
And a similar sounding bug that's affecting some users:
https://bugzilla.redhat.com/show_bug.cgi?id=1935331
--
Chris Murphy
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le
ere is the kernel's block core is confused
about it. I don't know why that would be. Does that EOD message happen
on every boot for sdb1?
--
Chris Murphy
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists
t; logical 498745085952 on dev /dev/sdb1
You're hitting the same bug as before. The errors only affect root 256
inode 257 path image, i.e. ext2_saved/image which is the rollback
image. No other files are affected. This bug isn't related to the
device size messages.
--
Chris Murphy
_
Also need:
sudo btrfs insp dump-s /dev/sda8 | grep 'total_bytes\|dev_item.total_bytes'
sudo btrfs insp dump-s /dev/sdb1 | grep 'total_bytes\|dev_item.total_bytes'
--
Chris
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an
ror message "1234 [
> 3341.845090] sdb: p1 size 1465144002 extends beyond EOD, enabling native
> capacity". Do you think this will cause the error condition from scrub that
> "we" are looking for?
What do you get for
fdisk -l /dev/sda
fdisk -l /dev/sdb
--
Ch
onal
That'll read every data and metadata block. Corruptions are reported
in dmesg. If there's redundancy (e.g. dup or raid1+) it'll try to
repair it from a good copy. Without a scrub, the same error detection
(and fixups if possible) happens passi
onal
That'll read every data and metadata block. Corruptions are reported
in dmesg. If there's redundancy (e.g. dup or raid1+) it'll try to
repair it from a good copy. Without a scrub, the same error detection
(and fixups if possible) happens passively as blocks are read.
--
Chris Murphy
__
On Fri, Mar 5, 2021 at 10:39 AM Chris Murphy wrote:
>
> Quick follow up on one thing I can't reproduce from George's scrub:
>
> [36365.549230] BTRFS error (device sda8): scrub: tree block
> 1777055424512 spanning stripes, ignored. logical=1777055367168
> [36365.549262] attemp
/mnt/btrfs/ext2_saved/image
e2image -Q /dev/loop1 /path/to/sda8ext4-e2image.bin
I estimate the file could be around 700MB (maybe up to 2G). It can be
compressed:
tar -S -acf sda8ext4-e2image.bin.tar.gz sda8ext4-e2image.bin
--
Chris Murphy
___
test
/ext2_saved/image /mnt/oldext4
That's it. You'll be able to inspect /mnt/oldext4 for the files you've
accidentally deleted. Of course you can't copy files to /mnt/btrfs
because it's read-only.
--
Chris Murphy
___
test mailing list -- test@lists.fedoraproject.org
On Wed, Mar 3, 2021 at 5:34 PM Matthew Miller wrote:
>
> On Wed, Mar 03, 2021 at 04:57:28PM -0700, Chris Murphy wrote:
> > It works at the block level. A block is read, checksum calculated and
> > compared to the previously recorded checksum for the block. It doesn't
> >
lace method in
effect creates a temporary virtual/hidden mirror, and does a scrub to
make the replacement the same as the source. File system writes during
replace go to both devices, and it's expected to be crash safe,
resuming automatically at next mount time.
--
Chris Murphy
__
spanning stripes, ignored. logical=1777055367168
> [36365.549262] attempt to access beyond end of device
>sda8: rw=0, want=3470811376, limit=3470811312
I'm not sure about this yet - need more info.
--
Chris Murphy
___
test mailing lis
reover, could you please direct me to some documentation on how to
> format the hard disk? Using GParted?
If you're already familiar with gparted, use that. Workstation edition
also comes with GNOME Disks, and KDE comes with Partition Manager,
which can also do t
idle-timeout="10m"
https://www.freedesktop.org/software/systemd/man/systemd.mount.html
https://www.freedesktop.org/software/systemd/man/systemd.automount.html#
--
Chris Murphy
___
users mailing list -- users@lists.fedoraproject.org
To uns
rent_Summary
QA:Testcase_base_reboot_unmount is listed 7 times, and 5 times it's as
milestone basic.
There is a btrfs specific portion of that test case that likewise lets
us know if previous reboots involved an unclean unmount, thus
indicating some kind of reboot problem.
--
On Fri, Feb 26, 2021 at 12:53 PM pmkel...@frontier.com
wrote:
>
>
>
> On 2/25/21 15:24, Chris Murphy wrote:
> >
> > An alternative is 'btrfs scrub start -BdR' which will not background
> > the scrub, and will give a detailed report upon completion.
> >
>
&g
st_size of the directory inode, and the
value is 2x the characters in all filenames in that directory. I'm not
sure if the names of directories are included in the count, or just
filenames.
--
Chris Murphy
___
devel mailing list -- devel@lists.fedorapr
the need to know when it's done. Progress indication might be
> good too.
dmesg will tell you when it's done as will 'btrfs scrub status'.
I suspect upstream would accept an enhancement for 'btrfs scrub start
-B' (don't background) such that it has a progress in
this one block, because I want to know
the big picture. The specific corruptions can provide clues for why
they are happening.
If this is the only bad block, there is a way to fix it with e2fs
tools. But getting a copy of this superblock before repairing it might
give a clue what stepped on it
status: 0
All errors will be between these two messages. Yours will have at
least one error for the "/mnt/ext2_saved/image" that we already know
about. What I want to know is if there's more problems before moving
on.
--
Chris Murphy
__
> this is an issue with F34 and rawhide's gnome-session package needing to be
> updated to include the commit previously referenced.
That sounds reasonable.
--
Chris Murphy
___
devel mailing list -- devel@lists.fedoraproject.org
To
On Sun, Feb 21, 2021 at 4:16 PM George R Goffe wrote:
>> On Sunday, February 21, 2021, 1:48:52 PM PST, Chris Murphy
>> wrote:
> That works for me. But you could alternatively try:
>
> mount /dev/vdb /mnt/btrfs
> losetup -r /dev/loop0 /mnt/btrfs/ext2_saved/
d I agree. But what I'm asking is *what
criterion*, i.e.
https://fedoraproject.org/wiki/Basic_Release_Criteria
https://fedoraproject.org/wiki/Fedora_34_Beta_Release_Criteria
https://fedoraproject.org/wiki/Fedora_34_Final_Release_Criteria
Bugs don't become blockers only because they're nasty bugs, t
b7a"
BLOCK_SIZE="4096" TYPE="ext4"
--
Chris Murphy
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject
On Sun, Feb 21, 2021 at 2:34 PM Chris Murphy wrote:
>
> On Sun, Feb 21, 2021 at 2:16 PM George R Goffe via test
> wrote:
> >
> > fc35-bash 5.1 ~# mount -t ext4 -o loop,ro /ext2_saved/image /ext4
> > mount: /ext4: can't read superblock on /dev/loop0.
>
> Hmm. Th
On Sun, Feb 21, 2021 at 2:16 PM George R Goffe via test
wrote:
>
> fc35-bash 5.1 ~# mount -t ext4 -o loop,ro /ext2_saved/image /ext4
> mount: /ext4: can't read superblock on /dev/loop0.
Hmm. That's unexpected though. I'm going to try it in a VM. It should work.
--
Chr
ing the filesystem to ext4.
Let's establish whether you deleted the file before or after
conversion? Depending on exactly when it was deleted makes a big
difference what the strategy for recovery is.
Once I know that I can answer more.
--
Chris Murphy
___
referred Target) is
Tue 2021-03-16. We've got 3-4 weeks to stabilize before we'd be out of
the lane.
https://fedorapeople.org/groups/schedule/f-34/f-34-key-tasks.html
--
Chris Murphy
___
test mailing list -- test@lists.fedoraproject.org
To unsubscrib
them in the middle of the
timeout! That's pretty curious and unexpected, but I don't know what
it means.
Some of "getting more and better information" on what's happening has
been discussed as a needed systemd enhancement. I'm not sure about the
time
On Tue, Feb 16, 2021 at 4:10 PM Jeremy Linton wrote:
> On 2/14/21 2:20 PM, Chris Murphy wrote:
> > This isn't sufficiently qualified. It does work to reduce space
> > consumption and write amplification. It's just that there's a tradeoff
> > that you dislike, which is I
501 - 600 of 8361 matches
Mail list logo
