ter the older system root, with just a few steps.
--
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-U
7;re going to
install is macOS, it will create a VM with UEFI firmware. If you repurpose such
a VM, or clone it, it'll still have UEFI firmware.
--
Chris Murphy
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send a
On Tue, Oct 10, 2023, at 11:25 PM, George R Goffe wrote:
> Chris,
>
> Thanks for responding.
>
> Here's the desired partition scheme:
>
> /boot
> /
> swap
> /var
> /opt
> /usr
> /export/home
It's missing /boot/efi which is required on
oot/efi as the mount point, is
formatted ext4 (or anything other than EFI file system, which off hand I forget
the term anaconda uses for this format).
--
Chris Murphy
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an em
n demand (and
unmount it after the timeout). If /boot is used in fstab, then /efi is used for
the ESP.
I'm pretty sure /efi doesn't exist unless you've (at one time or other)
configured sd-boot instead of grub.
--
Chris Murphy
__
he correct devices
> when /boot is on raid. It is very annoying though when this happens.
I don't know if https://github.com/coreos/bootupd is doing this automatically
on BIOS firmware systems now or is planning on doing it? At one time they were.
need to see the
systemd-oomd messages to see if there's a problem in the logic. It could also
be kernel related.
--
Chris Murphy
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fe
ew times per week,
> completely randomly, I can't reproduce it intentionally.
I haven't seen any gnome-shell crashes since before branch.
--
Chris Murphy
___
test mailing list -- test@lists.fedoraproject.org
To unsubs
nt in requiring grub2 to do
> something it cannot do.
An additional topic is having boot entries for Windows (and macOS) that don't
work in the meantime. While we could just remove the scripts that create these
entries to chainload another bootloader, they're still needed for BIO
on working group discussed it at today's meeting, and there were no
objections to the language change proposal.
--
Chris Murphy
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fed
y forward is
efibootmgr, and see if desktops want to add a GUI wrapper around it.
--
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://d
it fixed for release.
However, there's reluctance to broaden the scope of the criteria because our
influence has limits, including the infrastructure aspects of extensions that
we can't control (such as the web site itself). So we'd like to see this
covered under existing criter
f the problem is related to a
race condition, the problem may not happen. If that's the case you'll have to
do separate boots with one of the above parameters at a time to see which debug
method exposes the cause.
--
Chris Murphy
___
te
I've added a section how to modify /etc/kernel/cmdline in the snapshot before
rebooting.
https://fedoraproject.org/wiki/User:Chrismurphy/Draft/dualboot_teststation
--
Chris Murphy
___
test mailing list -- test@lists.fedoraproject.org
To unsubs
updates-testing for both 36
and 37, I'm no longer confident in this write up and have to retest. That
/etc/kernel/cmdline can contain stale information has broken this use case at
the moment, so I need to see if there's a better work arou
On Sun, Aug 21, 2022, at 2:31 PM, Chris Murphy wrote:
>
> https://fedoraproject.org/wiki/User:Chrismurphy/Draft/dualboot_teststation
I found a small problem, fixed in the latest version.
Gory details:
If you've ever used grubby, an /etc/kernel/cmdline file is created that
c
7;s
prior evidence of problems and what they might be. Because it sounds to me like
the hardware has become unreliable in some way.
--
Chris Murphy
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists
On Mon, Aug 22, 2022, at 11:47 AM, Chris Murphy wrote:
> On Mon, Aug 22, 2022, at 11:46 AM, Chris Murphy wrote:
>
>> After that, you can umount the file system. And mount again with '-o
>> rescue=usebackuproot' and hopefully it finds a good backup root, and
&
On Mon, Aug 22, 2022, at 11:46 AM, Chris Murphy wrote:
> After that, you can umount the file system. And mount again with '-o
> rescue=usebackuproot' and hopefully it finds a good backup root, and
> can fix itself. If it gets confused again, it'll go read only to avoi
sername normally using any
command you're familiar with.
After that, you can umount the file system. And mount again with '-o
rescue=usebackuproot' and hopefully it finds a good backup root, and can fix
itself. If it gets confused again, it'll go read only to avoid making
g;
* no installation step, instead system upgrade is used;
* reversibility, or undoability, i.e. with just a few steps you can delete the
"test OS".
https://fedoraproject.org/wiki/User:Chrismurphy/Draft/dualboot_teststation
--
Chris Murphy
__
arted, but
maybe
parted /dev/sdb disk_set pmbr_boot off
Now see if the stick boots the cranky hardware.
--
Chris Murphy
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
I'm getting: There are currently no products linked to this invitation code...
---
Chris Murphy
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct:
ich seems to work.
>
> Roger
>
> Am 01.04.22 um 19:46 schrieb Chris Murphy:
> > Bug is in samba.
> > https://bugzilla.redhat.com/show_bug.cgi?id=2068976
> >
> > --
> > Chris
> > ___
> > test mailing list -- t
Bug is in samba.
https://bugzilla.redhat.com/show_bug.cgi?id=2068976
--
Chris
___
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
On Wed, Mar 30, 2022 at 2:54 AM Zdenek Dohnal wrote:
>
> Hi all,
>
> On 3/29/22 23:25, Chris Murphy wrote:
> > * have a one time service delete all the printers, thereby forcing the
> > user to readd them, and then document this story
>
> The statements from above
37 (I'm not sure it's possible at this point, cc'd Zdenek)
* have a notification pop-up warn the user (this is probably an f37 timeframe)
* have a one time service delete all the printers, thereby forcing the
user to readd them, and then document t
e with both
current Fedora releases.
B. Release-blocking desktops must ship a version of Firefox [default
web browser] that avoids it being downgraded when performing a system
upgrade.
[1]
https://bugzilla.redhat.com/show_bug.cgi?id=2057193#c6
--
Chris Murphy
___
installer
3. Installation destination keep all defaults
4. Click blue text at the bottom "Full disk summary and boot loader..."
5. Select the (in my case single) drive, click the "Do not install
bootloader" button
6. Close and install
--
Chris Murphy
___
c_Release_Criteria#rpm-ostree_requirements
>
> because that is how things are designed to work, and it's clearly
> important enough that we should make it part of the release criteria
> that things actually work that way. But for traditional RPM-based
> installs, it doesn't real
7;s cheaper to require the two reboots. There
are other ways of updating being explored to reduce the reboot to one.
And reduce update frequency so that the compulsory reboots aren't
happening more than once every couple weeks, hopefully.
--
Chris Murphy
bvious statement about not breaking the system, which was implied in
> the past but I assumed it's better to have it clearly visible (this one could
> be moved to Beta, possibly).
>
> Finally it adds a requirement that the package manager must not mislead the
>
n the 35 cycle. Once
discovered, since nothing was actually broken, it was already too late.
--
Chris Murphy
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Cod
id=2032085
--
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/
List Guideli
On Wed, Nov 10, 2021 at 2:02 PM Chris Murphy wrote:
>
> My take, all except 6 are blocking.
Ooh I like this game where I don't read all the posts, and end up
agreeing with Kamil having not seen the answers first.
--
Chris Murphy
___
t
ating to a different screen, or
> clicking Install on pkg B (the particular action is not important in this
> scenario). That second action triggers a bug and pkg A installation is
> incorrectly aborted in a non-clean manner. The system ends up in an
&g
On Mon, Nov 8, 2021 at 11:39 AM Kamil Paral wrote:
>
> On Mon, Nov 8, 2021 at 4:28 PM Chris Murphy wrote:
>>
>> https://fedoraproject.org/wiki/Fedora_35_Final_Release_Criteria#Default_application_functionality
>>
>> "Basic functionality means that the app mus
pend (s2idle or S3) modes it should be?
But that's a question for kernel developers, and I guess the place to
start this is on the linux-usb@ list and see if /dev is supposed to be
consistent through suspend-to-ram.
--
Chris Murphy
een state).
If some offered functionality doesn't work, fix it or rip it out.
--
Chris Murphy
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct:
ht
On Wed, Oct 27, 2021, 8:18 PM Samuel Sieb wrote:
> On 10/27/21 17:02, Felix Miata wrote:
> > Chris Murphy composed on 2021-10-27 19:40 (UTC-0400):
> >
> >> Adam Williamson wrote:
> >>> On Wed, 2021-10-27 at 02:32 -0400, Felix Miata wrote:
> >
> > - package grub2-tools-minimal-1:2.06-6.fc35.x86_64 is filtered out by
> > exclude
> > filtering
> >
>
> Do you have soft dependencies enabled? Nothing on my installed system
> requires grubby, but two things recommend it: crypto-policies-scripts
> and kexe
hy F35 demands installation of grub2-tools-minimal and
> grubby,
> while F34 didn't?
What happens if you try dnf --disableexcludes=all ?
--
Chris Murphy
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an
s a kernel parameter, e.g.
grubby --args=drm.debug=0x06 --update-kernel=ALL
Reboot. Reproduce the problem. Hard reset (or possibly remote ssh will
still be functional). And then grab the log. To remove that boot
param:
grubby --remove-args=drm.debug=0x06 --update-kernel=ALL
--
Chris Murphy
_
On Tue, Sep 28, 2021 at 11:22 AM Peter Robinson wrote:
>
> On Mon, Sep 20, 2021 at 9:24 PM stan via test
> wrote:
> >
> > On Mon, 20 Sep 2021 08:39:38 -0600
> > Chris Murphy wrote:
> >
> > > Could you file a bug and include: e2fsprogs version; kernel v
different; and compete dmesg.
Once filed, post the URL here. Thanks
--
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:
t's go ahead and implement it. Only QA types would consider waiting
2 minutes for this just to (a) time it (b) see what happens, if
anything (c) try to find logs and/or some sort of work around. All
other mortals will properly hit the power button, give it all a second
go - which of course wi
https://bugzilla.redhat.com/show_bug.cgi?id=1963007
Add to meeting agenda?
This was brought up on the server list. Either something peculiar has
happened with this image, or the other netinstallers are soon to follow.
Either way we should probably figure it out.
Chris Murphy
letely separate set of servers. We were
on irc.freenode.net and now we're on irc.libera.chat - the channel
names are still the same. You will need to register your nick with
libera.chat.
--
Chris Murphy
___
test mailing list -- test@lists.fedor
uld show
what everyone is doing including if there's anything else especially
busy that's maybe slowing down whatever dnf is up to. It's
sufficiently verbose that it will fill up the kernel message buffer,
and likely a lot of messages will be dropped,
t'll need to get fixed before either the beta or
final milestone. And for that I use the blockerbugs app [3] to propose
it.
[1]
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/MAINTAINERS?h=v5.14-rc1
[2]
https://fedorapeople.org/groups/schedule/f-35/f-35-key-tasks.ht
e have no installable payload, they boot a sort of live image and
run the installer program. That's it. Server has different
partitioning defaults from Everything, but otherwise they're the same.
--
Chris Murphy
___
test mailing list -- test@lis
sponse, it doesn't work even when the network link is
> active.
Both of these are probably usability bugs, it should probably fail
faster when it's not finding something it recognizes... "is not a
valid source" or something to that effect. But before filing a bug it
might be
few other packages but no
> luck.
>
> Is it just my laptop that's somehow broken?
I've got a similar regression where the session starts in X instead of
Wayland, with a huge stack trace in the journal. So I don't think it's
hardware related.
--
Chris Murphy
___
On Sun, Jun 20, 2021 at 6:54 PM Chris Murphy wrote:
>
> 197 of these in the non-working instance
>
> 08:18:38,802 WARNING
> org.fedoraproject.Anaconda.Modules.Storage:WARNING:blivet:device/model
> is not a valid attribute
>
> 2 in the working instance. Seems suspicious.
&g
FI VM, has an ESP and UEFI GRUB. But it's being tested
in openqa in a BIOS VM so it fails. But I'm not sure why it's being
created in a UEFI VM...
--
Chris Murphy
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send
loppy /dev/vda
So it should be in the 34 log too, right? And yet it's not. So that'd
explain why it doesn't have a bootloader. Not sure why it wasn't even
executed though, almost like the installation is just missing a bunch
of steps?
--
Chris Murphy
__
On Sun, Jun 20, 2021 at 6:21 PM Chris Murphy wrote:
>
> https://openqa.fedoraproject.org/tests/912650
>
> Does openqa only do qcow2 tests? I'm not seeing raw tests. I'm just
> curious for another data point. :P
>
> I'm seeing Rawhide and 33 images passing (cou
e all failing
at the firmware as if it's not finding a bootloader at all. Hence
wondering if there might be a difference between raw and qcow2...
--
Chris Murphy
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe
de6a170af.3886918.162089360600.zst"
> is not a core dump: file format not recognized
Yes, file a bug against gdb.
Thanks,
--
Chris Murphy
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le.
have rawhide kernels, because the kernel is special. Your other
packages won't get f34 versions because that would be a downgrade.
I think.
--
Chris Murphy
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to te
cause there's test cases to make sure these are tested.
--
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
eports of grub> prompt following upgrades.
--
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/
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
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
__
gt;>> 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.fedoraproj
d
shoring up. And the bootloaders 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
_
dle /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://do
d cover most 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 --
xed' option for
file 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/p
so the interoperability 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 singl
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 F35
h to the Branched
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
___
volume. I'd say
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.fedora
AM...
smartctl -x will report quite a lot more information about a drive,
including 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
sudo -i
cd /var/lib/dnf/
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.fe
: 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
o report the
lockdep warnings. 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
__
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
nly discrepancy here 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 a
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 emai
maller drive now and see an error 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/
#optional
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.
--
Chr
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.5492
ev/sda8 /mnt/btrfs
losetup -r /dev/loop1 /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
unt -o ro,loop /mnt/btrfs/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
___
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
>
d' followed by 'btrfs device remove'. The replace 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,
resumi
"I can't fix it".
> [36365.549230] BTRFS error (device sda8): scrub: tree block 1777055424512
> spanning stripes, ignored. logical=1777055367168
> [36365.549262] attempt to access beyond end of device
>sda8: rw=0, want=3470811376, limit=3470811312
I'm
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
n the computer until it completes?
>
> Yes hence 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 f
now if
there's more corruption than 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
): scrub: finished on devid 1
with 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
__
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/
-7418d71b5b7a"
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.fed
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.
>
> Hm
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 w
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
__
Preferred 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
T
1 - 100 of 1217 matches
Mail list logo
