Re: Fedora 34 dns resolution problems?

[Joe Zeff]

On 1/2/21 9:06 PM, Ed Greshko wrote:
First thing.  Try not starting a line with "--".  Some email client 
interpret that as the start of the

signature block and screws up presentation and reply formatting.


Actually, it's "-- " and that space matters.  Any email clients that 
ignore that are borken.

___
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-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: btrfs RAID 5?

[Chris Murphy]

On Sat, Jan 2, 2021 at 11:55 AM Richard Shaw  wrote:
>
> From what I've been able to find online it doesn't look like RAID 5 is well 
> supported by btrfs currently. Anyone have any data to the contrary?

There are caveats. If you can live with them, then it's OK. But
obligatory reading:
https://lore.kernel.org/linux-btrfs/20200627032414.gx10...@hungrycats.org/

You definitely want metadata raid1, and use free space tree
(space_cache v2) for this setup. A top use case and expectation is the
uptime in the face of a device failure. If you're able to quickly do a
'btrfs replace' (another requirement, don't use 'dev add' + 'dev
remove') then it might be OK.

> I have a 4TB media drive that's filling up and I'd like to add two more disks 
> to both increase capacity and add some redundancy. My understanding is that 
> if I did a 3 drive btrfs RAID 1 that I would just have 3 copies of the same 
> data and zero increased capacity.

No. Btrfs raid1 is exactly two copies no matter how many drives are in
the pool. There's raid1c3 for three copies, and raid1c4 for four
copies. A three device btrfs raid1 is valid.

Btrfs does not do raid at a block level like md raid. It's at the
block group level. A block group is a ~1G contiguous region of
extents. You could consider the block group a super extent, similar to
how an extent is a collection of blocks. Like extent size, the block
group size isn't fixed, but generally it appears in 1G amounts.

The block group "profile" is what determines the number and behavior
of chunks that get allocated to various devices. A chunk is the
physical manifestation of a block group on actual devices. The single
profile means 1:1 block group to chunk. The dup profile means 1:2
block group to chunk *on the same device*. The raid1 profile also is
1:2 block group to chunk but on different devices. And how this gets
allocated depends mainly on free space remaining. So it is possible
for a block group with raid1 profile to be allocated with mirror
chunks on drive A and B, and for the very next block group allocated
will be chunks on drives B and C.

This is why free space reporting on Btrfs can be confusing. Even
number of same sized drives with raid1 is OK, but then odd number of
drives or mix and match drive sizes and it gets screwy, even though
it's valid and Btrfs will use Tetris technique to fill in the free
space wherever it is.

https://github.com/kdave/btrfs-progs/issues/277

https://carfax.org.uk/btrfs-usage/




-- 
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-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Fedora 34 dns resolution problems?

[Michael H. Warfield]

On Sun, 2021-01-03 at 12:06 +0800, Ed Greshko wrote:
> On 03/01/2021 11:52, Michael H. Warfield wrote:

> First thing.  Try not starting a line with "--".  Some email
> client interpret that as the start of the
> signature block and screws up presentation and reply formatting.

That's good to note but classically the convention is suppose to be "--
" (with an explicit trailing hard space that some damn MUI's tend to
drop).  I try to use three dashes and space "--- " to indicate
preformatted text but I may have screwed up there.  My apologies if
that's the case.

> > But no...  systemd-resolved is not running and is not
> > enabled.  Not the problem.  Which makes it even more perplexing.

> > Not a symlink.  Didn't work even when it was and redirected to
> > 127.0.0.253.  One of the first things I check and tried.  Also
> > checked
> > nsswitch.conf.  Some differences but not that I could spot and why
> > the
> > difference between "host" and "ping"?  And why the timeout???
> > 
> > nsswitch.conf  hosts:  files mdns4_minimal [NOTFOUND=return]
> > resolve [!UNAVAIL=return] myhostname dns

> I don't know if this will have any effect, but since you're not
> running/using systemd-resolved then it may be
> a good idea to remove "resolve" from nsswitch.conf.

Noted.  Many thanks.  Next thing to test.  Good to know.

> An F32 system has

> hosts:  files mdns4_minimal [NOTFOUND=return] dns myhostnam

Yeah, I had noticed that.  Again thanks.

> ---
> The key to getting good answers is to ask good questions.

Regards,
Mike
-- 
Michael H. Warfield (AI4NB) | (o) +1 706 850-8773 |  m...@wittsend.com
   /\/\|=mhw=|\/\/  | (c) +1 678 463-0932 |  
http://www.wittsend.com/mhw/
ARIN whois: MHW9-ARIN   | An optimist believes we live in the best of all
PGP Key: 0xC0EB9675674627FF | possible worlds.  A pessimist is sure of it!


signature.asc
Description: This is a digitally signed message part
___
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-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Fedora 34 dns resolution problems?

[Michael H. Warfield]

On Sun, 2021-01-03 at 12:10 +0800, Ed Greshko wrote:
> On 03/01/2021 12:06, Michael H. Warfield wrote:
> > Note, I did try "ping6" to differentiate.  Even though there was an
> > IPv6 address, it still failed with "unknown host or service".

> You indicated "I'm fully IPv6 enabled".

Yes.  I'm the author of a number of white papers on the subject dating
back to 1999 and refused to publish until I could claim to be globally
visible on IPv6.  It's not an option to me.

> In that case "ping" and "ping6" would both try IPv6 addresses.  So,
> there is no difference.

That is correct.  But the error message indicates a failure to resolve,
not a failure to route.

> ---
> The key to getting good answers is to ask good questions.

I think your other response on nsswitch.conf may be the thread I need
to pick at.  I'm off to test it now.

Many thanks

Regards,
Mike
-- 
Michael H. Warfield (AI4NB) | (o) +1 706 850-8773 |  m...@wittsend.com
   /\/\|=mhw=|\/\/  | (c) +1 678 463-0932 |  
http://www.wittsend.com/mhw/
ARIN whois: MHW9-ARIN   | An optimist believes we live in the best of all
PGP Key: 0xC0EB9675674627FF | possible worlds.  A pessimist is sure of it!


signature.asc
Description: This is a digitally signed message part
___
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-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Migration to btrfs: Is a reinstall the best way?

[Chris Murphy]

On Sat, Jan 2, 2021 at 9:04 AM Richard Shaw  wrote:
>
> My plan is to upgrade from my current 500GB Samsung EVO to a 1TB version and 
> copy all my data over.
>
> Creating the subvolumes and updating fstab is easy enough, but what else 
> needs to be done?

grub2-mkconfig. The root fs UUID has changed as well as needs a hint
for the subvolume to use as sysroot, e.g. rootflags=subvol=root. These
are picked up by grub2-mkconfig.

initramfs probably does not need to be done, because btrfs is now
built-in to the kernel instead of as a module.

> Would a reinstall do any "magic" that's difficult to do by hand?

Not really. When in doubt use defaults. And the installer uses
upstream defaults.

Two features will soon be the default, are stable for a long time, and
I use them both. Since you're doing your own mkfs you could opt in
now: '-R free-space-tree -O no-holes'  - both can be enabled after
mfks time though too.


-- 
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-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Fedora 34 dns resolution problems?

[Ed Greshko]

On 03/01/2021 12:06, Michael H. Warfield wrote:

Note, I did try "ping6" to differentiate.  Even though there was an
IPv6 address, it still failed with "unknown host or service".


You indicated "I'm fully IPv6 enabled".

In that case "ping" and "ping6" would both try IPv6 addresses.  So, there is no 
difference.

---
The key to getting good answers is to ask good questions.
___
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-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Fedora 34 dns resolution problems?

[Michael H. Warfield]

On Sun, 2021-01-03 at 11:54 +0800, Ed Greshko wrote:
> On 03/01/2021 06:30, Michael H. Warfield wrote:
> > [mhw@rpi-plate ~]$ ping mirrors.fedoraproject.org
> > ping: mirrors.fedoraproject.org: Name or service not known
> > [mhw@rpi-plate ~]$ ping6 mirrors.fedoraproject.org
> > ping6: mirrors.fedoraproject.org: Name or service not known
> 
> Just a note here.
> 
> If you do have IPv6 service, those addresses will be preferred over
> IPv4.  See man gai.conf.
> One would have to do "ping -4" to differentiate.

Note, I did try "ping6" to differentiate.  Even though there was an
IPv6 address, it still failed with "unknown host or service".

> [egreshko@meimei ~]$ ping -c 1 mirrors.fedoraproject.org
> PING mirrors.fedoraproject.org(proxy06.fedoraproject.org
> (2605:bc80:3010:600:dead:beef:cafe:fed9)) 56 data bytes
> 64 bytes from proxy06.fedoraproject.org
> (2605:bc80:3010:600:dead:beef:cafe:fed9): icmp_seq=1 ttl=53 time=148
> ms

> [egreshko@meimei ~]$ ping -4 -c 1 mirrors.fedoraproject.org
> PING  (8.43.85.67) 56(84) bytes of data.
> 64 bytes from proxy14.fedoraproject.org (8.43.85.67): icmp_seq=1
> ttl=42 time=199 ms

Right now, "Slide" and "Rpi-Plate" are communicating...  Both work...
 I'm fully IPv6 enabled.  I'll have to wait a day or so till the
faceplant again.

[root@slide eero]# ping -4 mirrors.fedoraproject.org
PING  (140.211.169.206) 56(84) bytes of data.
64 bytes from proxy09.fedoraproject.org (140.211.169.206): icmp_seq=1 ttl=48 
time=98.2 ms
64 bytes from proxy09.fedoraproject.org (140.211.169.206): icmp_seq=2 ttl=48 
time=97.6 ms
^C
---  ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1002ms
rtt min/avg/max/mdev = 97.601/97.882/98.164/0.281 ms
[root@slide eero]# ping mirrors.fedoraproject.org
PING mirrors.fedoraproject.org(2620:52:3:1:dead:beef:cafe:fed6 
(2620:52:3:1:dead:beef:cafe:fed6)) 56 data bytes
64 bytes from 2620:52:3:1:dead:beef:cafe:fed6 
(2620:52:3:1:dead:beef:cafe:fed6): icmp_seq=1 ttl=53 time=63.9 ms
64 bytes from 2620:52:3:1:dead:beef:cafe:fed6 
(2620:52:3:1:dead:beef:cafe:fed6): icmp_seq=2 ttl=53 time=38.0 ms
^C
--- mirrors.fedoraproject.org ping statistics ---
3 packets transmitted, 2 received, 33.% packet loss, time 2003ms
rtt min/avg/max/mdev = 38.016/50.936/63.856/12.920 ms


> ---
> The key to getting good answers is to ask good questions.

Regards,
Mike
-- 
Michael H. Warfield (AI4NB) | (o) +1 706 850-8773 |  m...@wittsend.com
   /\/\|=mhw=|\/\/  | (c) +1 678 463-0932 |  
http://www.wittsend.com/mhw/
ARIN whois: MHW9-ARIN   | An optimist believes we live in the best of all
PGP Key: 0xC0EB9675674627FF | possible worlds.  A pessimist is sure of it!


signature.asc
Description: This is a digitally signed message part
___
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-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Fedora 34 dns resolution problems?

[Ed Greshko]

On 03/01/2021 11:52, Michael H. Warfield wrote:

First thing.  Try not starting a line with "--".  Some email client 
interpret that as the start of the
signature block and screws up presentation and reply formatting.



But no...  systemd-resolved is not running and is not
enabled.  Not the problem.  Which makes it even more perplexing.

Not a symlink.  Didn't work even when it was and redirected to
127.0.0.253.  One of the first things I check and tried.  Also checked
nsswitch.conf.  Some differences but not that I could spot and why the
difference between "host" and "ping"?  And why the timeout???

nsswitch.conf  hosts:  files mdns4_minimal [NOTFOUND=return] resolve 
[!UNAVAIL=return] myhostname dns


I don't know if this will have any effect, but since you're not running/using 
systemd-resolved then it may be
a good idea to remove "resolve" from nsswitch.conf.

An F32 system has

hosts:  files mdns4_minimal [NOTFOUND=return] dns myhostnam

---
The key to getting good answers is to ask good questions.

___
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-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Fedora 34 dns resolution problems?

[Michael H. Warfield]

On Sun, 2021-01-03 at 11:30 +0800, Ed Greshko wrote:
> On 03/01/2021 08:57, Sam Varshavchik wrote:
> > Michael H. Warfield writes:
> > 
> > > Fedora 34 and the Fedora 33).  All on the same network.  All with
> > > the
> > > same name servers for resolution.
> > > 
> > > /etc/resolv.conf
> > > -- 
> > > # Generated by NetworkManager
> > > search wittsend.com
> > > nameserver 8.8.8.8
> > > nameserver 1.1.1.1
> > > nameserver 10.205.38.3
> > > -- 

> > Is /etc/resolv.conf a symlink, and if so where is it pointing.

> You are thinking it is connected with systemd-resolved?

That was my first thought, given my legendary attitude toward the borg
systemd in general (when do we get systemd-mine-sweeper?).  Lennart
Pottering and I almost got physical at one Linux Plumbers over some of
their screwups.  But no...  systemd-resolved is not running and is not
enabled.  Not the problem.  Which makes it even more perplexing.

> If /etc/resolv.conf were a symlink it would contain

> # This file is managed by man:systemd-resolved(8). Do not edit.

> and not

> # Generated by NetworkManager

Not a symlink.  Didn't work even when it was and redirected to
127.0.0.253.  One of the first things I check and tried.  Also checked
nsswitch.conf.  Some differences but not that I could spot and why the
difference between "host" and "ping"?  And why the timeout???

nsswitch.conf

-- 
hosts:  files mdns4_minimal [NOTFOUND=return] resolve [!UNAVAIL=return] 
myhostname dns
--

> ---
> The key to getting good answers is to ask good questions.

Agreed!  And that is the thread I'm trying to pick at.  What is the
right question?

Regards,
Mike
-- 
Michael H. Warfield (AI4NB) | (o) +1 706 850-8773 |  m...@wittsend.com
   /\/\|=mhw=|\/\/  | (c) +1 678 463-0932 |  
http://www.wittsend.com/mhw/
ARIN whois: MHW9-ARIN   | An optimist believes we live in the best of all
PGP Key: 0xC0EB9675674627FF | possible worlds.  A pessimist is sure of it!


signature.asc
Description: This is a digitally signed message part
___
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-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Fedora 34 dns resolution problems?

[Ed Greshko]

On 03/01/2021 06:30, Michael H. Warfield wrote:

[mhw@rpi-plate ~]$ ping mirrors.fedoraproject.org
ping: mirrors.fedoraproject.org: Name or service not known
[mhw@rpi-plate ~]$ ping6 mirrors.fedoraproject.org
ping6: mirrors.fedoraproject.org: Name or service not known


Just a note here.

If you do have IPv6 service, those addresses will be preferred over IPv4.  See 
man gai.conf.
One would have to do "ping -4" to differentiate.

[egreshko@meimei ~]$ ping -c 1 mirrors.fedoraproject.org
PING mirrors.fedoraproject.org(proxy06.fedoraproject.org 
(2605:bc80:3010:600:dead:beef:cafe:fed9)) 56 data bytes
64 bytes from proxy06.fedoraproject.org 
(2605:bc80:3010:600:dead:beef:cafe:fed9): icmp_seq=1 ttl=53 time=148 ms

[egreshko@meimei ~]$ ping -4 -c 1 mirrors.fedoraproject.org
PING  (8.43.85.67) 56(84) bytes of data.
64 bytes from proxy14.fedoraproject.org (8.43.85.67): icmp_seq=1 ttl=42 
time=199 ms


---
The key to getting good answers is to ask good questions.

___
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-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Fedora 34 dns resolution problems?

[Michael H. Warfield]

On Sat, 2021-01-02 at 19:57 -0500, Sam Varshavchik wrote:
> Michael H. Warfield writes:

> > Fedora 34 and the Fedora 33).  All on the same network.  All with
> > the
> > same name servers for resolution.

> > /etc/resolv.conf
> > --
> > # Generated by NetworkManager
> > search wittsend.com
> > nameserver 8.8.8.8
> > nameserver 1.1.1.1
> > nameserver 10.205.38.3
> > --

> Is /etc/resolv.conf a symlink, and if so where is it pointing.


NO!  That's the first thing I checked and FIXED.  Again, same thing in
F32 and F33.  What's changed?

Regards,
Mike
-- 
Michael H. Warfield (AI4NB) | (o) +1 706 850-8773 |  m...@wittsend.com
   /\/\|=mhw=|\/\/  | (c) +1 678 463-0932 |  
http://www.wittsend.com/mhw/
ARIN whois: MHW9-ARIN   | An optimist believes we live in the best of all
PGP Key: 0xC0EB9675674627FF | possible worlds.  A pessimist is sure of it!


signature.asc
Description: This is a digitally signed message part
___
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-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Fedora 34 dns resolution problems?

[Ed Greshko]

On 03/01/2021 08:57, Sam Varshavchik wrote:

Michael H. Warfield writes:


Fedora 34 and the Fedora 33).  All on the same network.  All with the
same name servers for resolution.

/etc/resolv.conf
--
# Generated by NetworkManager
search wittsend.com
nameserver 8.8.8.8
nameserver 1.1.1.1
nameserver 10.205.38.3
--


Is /etc/resolv.conf a symlink, and if so where is it pointing.



You are thinking it is connected with systemd-resolved?

If /etc/resolv.conf were a symlink it would contain

# This file is managed by man:systemd-resolved(8). Do not edit.

and not

# Generated by NetworkManager

---
The key to getting good answers is to ask good questions.

___
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-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Backing up Btrfs (was: btrfs or ext4)

[Chris Murphy]

On Sat, Jan 2, 2021 at 6:27 AM Patrick O'Callaghan
 wrote:
>
> Brief recap: I'm currently using BorgBackup, which among other things
> does compression and deduplication. I'm looking at the pros and cons of
> changing to Btrfs for backup (I already use it as my main fs). The
> backup drives are currently ext4 so would need to be converted.
>
> Now read on.
>
> Following Chris Murphy's suggestion, I looked at:
>
> https://fedoramagazine.org/btrfs-snapshots-backup-incremental/
>
> My question is whether I can use compression and deduplication on the
> backup even if these have not been enabled on the original fs. My
> instinct is to say no, but I could be wrong.

You can use compression and/or dedup on the backup even if they are
not used on the original file system (whether ext4 or Btrfs).

Compression is just a mount option on Btrfs. [1] The current version
of the Btrfs send stream is not compressed. [2]

Btrfs dedup is "out-of-band" in that the file system is mounted, but
the dedup is not live. Writes, including duplicates, get written to
disk, and are later submitted for deduplication by a utility like
duperemove (in Fedora repo) or Bees. [3]

The way reflinks (efficient copies), snapshots, and dedup relate to
each other, is they all result in shared extents. The actions for
arriving at shared extents differ quite a bit. What makes btrfs
different from other file systems, and how it relates to send/receive,
is it has the ability to cheaply compute differences between
snapshots, without requiring deep traversal on either the send or
receive file systems.

The less your /home changes, the more convenient it is to keep the
backup up to date, because the cost of figuring out what to back up is
so chea. If your ~/ contains many things that change that you don't
care about backing up, then most any other backup solution provides
"excludes" to filter out such things. Btrfs send/receive doesn't have
such a thing. The closest approximation is you can create a nested
subvolume in place of a directory to create a snapshot boundary,
because btrfs snapshots are not recursive into subvolumes. e.g.  you
could create a new ~/.cache subvolume to substitute the directory. It
could be a ~1G of savings just for the Firefox cache alone.

Note: subvolumes have their own pool of inodes, they're separate file
trees not separate file systems, but can sometimes behave like a
separate file system. Programs like rsync and find will include
subvolumes by default unless you use -x or -xdev respectively. There's
an equivalent option in borgbackup which is enabled by default. So it
excludes nested subvolumes and snapshots by default. Part of the
reasoning for this is that folks with many snapshots were finding that
their backup program sees each snapshot as a completely separate and
massive pile of files subject to being backed up. Sooo yeah...
something to watch out for. If you ask borg to backup /, therefore it
will not automatically backup /home because it's considered a separate
"file system". Whew...


--
Chris Murphy


[1] You can change the compression option while mounted by using the
remount option along with the new compression values you want. Mix and
match is valid. Whatever is set at the time of writing, is what's
being used. If you forget to mount with compression, then those writes
aren't compressed. Etc.

[2] There are patches upstream that will persist compression in the
stream; it's preliminary work to support native encryption which will
likewise preserve encryption in the send stream. This means we'll be
able to replicate snapshots even if they aren't unlocked, and the
replication uses the same key as the original. Stay turned.

[3] https://github.com/Zygo/bees


-- 
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-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: usb stick problem

[Tom Horsley]

On Sat, 2 Jan 2021 18:33:23 -0700
Chris Murphy wrote:

> My opinion is
> anything brand new that has even one error, send it back. It's not
> like it's gonna get better with age!

It always seems to take at least a week for my cheap USB sticks
to go bad :-).
___
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-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: usb stick problem

[Chris Murphy]

Slight tangent, but once getting new flash, test it.

I recommend using f3 on any new USB stick. It's in Fedora repo. The
project is originally intended to identify fake flash. It'll report a
larger capacity than it has flash memory for, and has firmware that
does a loop. Super convenient that if you never hit the loop, you
don't find out; and if you hit the loop, it overwrites and corrupts
earlier data - sad panda. But it also will test for any kind of
corruptions or read errors, not just bogus flash.

It's also reasonable to use it for "burning in" hard drives - it's
just writing a bunch of pattern tests and reading them back in. It
doesn't matter what file system you use to format the device. Format,
mount, f3write /mnt then f3read /mnt. That's it. My opinion is
anything brand new that has even one error, send it back. It's not
like it's gonna get better with age!

Details:
https://github.com/AltraMayor/f3
https://fight-flash-fraud.readthedocs.io/en/latest/

--
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-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Fedora 34 dns resolution problems?

[Sam Varshavchik]

Michael H. Warfield writes:


Fedora 34 and the Fedora 33).  All on the same network.  All with the
same name servers for resolution.

/etc/resolv.conf
--
# Generated by NetworkManager
search wittsend.com
nameserver 8.8.8.8
nameserver 1.1.1.1
nameserver 10.205.38.3
--


Is /etc/resolv.conf a symlink, and if so where is it pointing.





pgpTvE5LPoI6d.pgp
Description: PGP signature
___
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-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Fedora 34 dns resolution problems? - should be 33

[Michael H. Warfield]

On Sat, 2021-01-02 at 19:04 -0500, Tom Horsley wrote:
> On Sat, 02 Jan 2021 18:18:30 -0500
> Michael H. Warfield wrote:
> 
> > Problem is still real.
> 
> I doubt it is the same issue, but I had DNS go out on my phone
> the other day, and eventually (after much confusion) discovered
> that the DNS info in my router wasn't saved when I upgraded the
> firmware, so when it provided a DNS server via DHCP, it didn't
> provide my local DNS server as the one to use, so everything
> on my local network became invisible to anything that got a new
> DHCP lease (and my phone was the first thing I noticed not working).

Yeah, not the same issue.  My current DHCP server is on one of those
RPi's and the previous one was on an RPi 3 which still runs Fedora 32.
 Doesn't explain why Fedora 32 behaves one way and 33 does this on the
same network with the same dhcp servers and routers.  :-P

The configs where duplicated between the two RPi's but it's had no
influence on the strange behavior of the Fedora 33 systems.  I may spin
up and x86_64 LXC container on my big server to test it out on that
arch.  Weird weird feces.

Thanks for the feedback.

Regards,
Mike
-- 
Michael H. Warfield (AI4NB) | (o) +1 706 850-8773 |  m...@wittsend.com
   /\/\|=mhw=|\/\/  | (c) +1 678 463-0932 |  
http://www.wittsend.com/mhw/
ARIN whois: MHW9-ARIN   | An optimist believes we live in the best of all
PGP Key: 0xC0EB9675674627FF | possible worlds.  A pessimist is sure of it!


signature.asc
Description: This is a digitally signed message part
___
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-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Fedora 34 dns resolution problems? - should be 33

[Tom Horsley]

On Sat, 02 Jan 2021 18:18:30 -0500
Michael H. Warfield wrote:

> Problem is still real.

I doubt it is the same issue, but I had DNS go out on my phone
the other day, and eventually (after much confusion) discovered
that the DNS info in my router wasn't saved when I upgraded the
firmware, so when it provided a DNS server via DHCP, it didn't
provide my local DNS server as the one to use, so everything
on my local network became invisible to anything that got a new
DHCP lease (and my phone was the first thing I noticed not working).
___
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-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Fedora 34 dns resolution problems? - should be 33

[Michael H. Warfield]

Sorry...  Getting confused in my old age...

s/33/32/g
s/34/33/g

Got my revs out of sink.  Problem is still real.  Trying the trick of
beating NetworkManager into submission with "dns=none" I pulled off
this list.

Thanks!

Regards,
Mike

On Sat, 2021-01-02 at 17:30 -0500, Michael H. Warfield wrote:
> I'm not even sure what to file a bug against.  This makes no sense to
> me.
> 
> I have four Raspberry Pi's on Fedora 34.  One RPi4 and Three RPi3s,
> all
> running aarch 64.  I also have numerous other RPi's on Fedora 33
> aarch64 that are running just fine, parallel configurations.  I'm not
> upgrading any of my X86_64 systems until I know the root cause of
> this.
> 
> If the Fedora 34 systems are up more than a day and I go to update I
> get things like this...
> 
> -- 
> rror: Curl error (6): Couldn't resolve host name for 
> https://mirrors.fedoraproject.org/metalink?repo=fedora-modular-33=aarch64
> [Could not resolve host: mirrors.fedoraproject.org] (
> https://mirrors.fedoraproject.org/metalink?repo=fedora-modular-33=aarch64
> ).
> error: Curl error (6): Couldn't resolve host name for 
> https://mirrors.fedoraproject.org/metalink?repo=fedora-modular-33=aarch64
> [Could not resolve host: mirrors.fedoraproject.org] (
> https://mirrors.fedoraproject.org/metalink?repo=fedora-modular-33=aarch64
> ).
> error: Curl error (6): Couldn't resolve host name for 
> https://mirrors.fedoraproject.org/metalink?repo=fedora-modular-33=aarch64
> [Could not resolve host: mirrors.fedoraproject.org] (
> https://mirrors.fedoraproject.org/metalink?repo=fedora-modular-33=aarch64
> ).
> error: Curl error (6): Couldn't resolve host name for 
> https://mirrors.fedoraproject.org/metalink?repo=fedora-modular-33=aarch64
> [Could not resolve host: mirrors.fedoraproject.org] (
> https://mirrors.fedoraproject.org/metalink?repo=fedora-modular-33=aarch64
> ).
> error: Curl error (6): Couldn't resolve host name for 
> https://mirrors.fedoraproject.org/metalink?repo=fedora-modular-33=aarch64
> [Could not resolve host: mirrors.fedoraproject.org] (
> https://mirrors.fedoraproject.org/metalink?repo=fedora-modular-33=aarch64
> ).
> -- 
> 
> And this...
> 
> -- 
> [mhw@rpi-plate ~]$ host mirrors.fedoraproject.org
> mirrors.fedoraproject.org is an alias for wildcard.fedoraproject.org.
> wildcard.fedoraproject.org has address 152.19.134.198
> wildcard.fedoraproject.org has address 8.43.85.67
> wildcard.fedoraproject.org has address 209.132.190.2
> wildcard.fedoraproject.org has address 152.19.134.142
> wildcard.fedoraproject.org has address 140.211.169.206
> wildcard.fedoraproject.org has address 8.43.85.73
> wildcard.fedoraproject.org has address 38.145.60.20
> wildcard.fedoraproject.org has address 38.145.60.21
> wildcard.fedoraproject.org has address 140.211.169.196
> wildcard.fedoraproject.org has address 67.219.144.68
> wildcard.fedoraproject.org has IPv6 address
> 2620:52:3:1:dead:beef:cafe:fed6
> wildcard.fedoraproject.org has IPv6 address
> 2604:1580:fe00:0:dead:beef:cafe:fed1
> wildcard.fedoraproject.org has IPv6 address
> 2605:bc80:3010:600:dead:beef:cafe:fed9
> wildcard.fedoraproject.org has IPv6 address
> 2620:52:3:1:dead:beef:cafe:fed7
> wildcard.fedoraproject.org has IPv6 address
> 2610:28:3090:3001:dead:beef:cafe:fed3
> wildcard.fedoraproject.org has IPv6 address
> 2605:bc80:3010:600:dead:beef:cafe:feda
> [mhw@rpi-plate ~]$ ping mirrors.fedoraproject.org
> ping: mirrors.fedoraproject.org: Name or service not known
> [mhw@rpi-plate ~]$ ping6 mirrors.fedoraproject.org
> ping6: mirrors.fedoraproject.org: Name or service not known
> 
> -- 
> 
> Checking /etc/resolv.conf looks good (host works) and nsswitch.conf
> looks good.  Doesn't seem to depend on whether I use static name
> servers or dhcp served name servers (I have some of each on both the
> Fedora 34 and the Fedora 33).  All on the same network.  All with the
> same name servers for resolution.
> 
> /etc/resolv.conf
> -- 
> # Generated by NetworkManager
> search wittsend.com
> nameserver 8.8.8.8
> nameserver 1.1.1.1
> nameserver 10.205.38.3
> -- 
> 
> Restarting NetworkManager - no help
> 
> Rebooting the system restores normal operation for anywhere from
> several hours to a day before it happens again.
> 
> WTH changed between 33 and 34 to create this problem?  Anybody got
> any
> suggestions where to look?  None, I mean not a single solitary one of
> my Fedora 33 systems, x86_64, arm7l (RPi 2's), or aarch64's are
> behaving this way but all 4 of my Fedora 34 systems are.
> 
> Regards,
> Mike
-- 
Michael H. Warfield (AI4NB) | (o) +1 706 850-8773 |  m...@wittsend.com
   /\/\|=mhw=|\/\/  | (c) +1 678 463-0932 |  
http://www.wittsend.com/mhw/
ARIN whois: MHW9-ARIN   | An optimist believes we live in the best of all
PGP Key: 0xC0EB9675674627FF | possible worlds.  A pessimist is sure of it!


signature.asc
Description: This is a digitally signed message part
___
users mailing list -- users@lists.fedoraproject.org
To 

Re: usb stick problem

[Kostas Sfakiotakis]

Στις 3/1/21 12:32 π.μ., ο/η Ed Greshko έγραψε:

On 03/01/2021 06:11, Matthew Miller wrote:

On Sat, Jan 02, 2021 at 11:48:00PM +0200, Kostas Sfakiotakis wrote:

Am trying to plug a usb memory stick onto my computer .

 From the looks of it , at first it looks that it gets recognized up
to a point , initially it gets asigned letter "f" /dev/sdf
but then some error pop up and i can't see it on dolphin or access
it somehow .

The attached files contains the relevant messages but i don't
understand what it says .

Well, it boils down to the errors saying the device isn't responding
properly. Are the contents of the stick important? I'd toss it into the
e-waste and get another.


I'd first plug it into a different USB slot.  If a desktop with front 
and rear connections I'd try an

opposite one.



Well i have tried both on a usb-hub that i have here and on a couple of 
rear usb ports that i have on this system.

It always failed to work with the same messages .


___
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-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: usb stick problem

[Kostas Sfakiotakis]

+

Στις 3/1/21 12:11 π.μ., ο/η Matthew Miller έγραψε:

On Sat, Jan 02, 2021 at 11:48:00PM +0200, Kostas Sfakiotakis wrote:

Am trying to plug a usb memory stick onto my computer .

 From the looks of it , at first it looks that it gets recognized up
to a point , initially it gets asigned letter "f" /dev/sdf
but then some error pop up and i can't see it on dolphin or access
it somehow .

The attached files contains the relevant messages but i don't
understand what it says .

Well, it boils down to the errors saying the device isn't responding
properly. Are the contents of the stick important? I'd toss it into the
e-waste and get another.



It's empty  , so i guess it can be tossed .
___
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-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: How can I downgrade e2fsprogs ? resize2fs returned an error (1)!

[Ed Greshko]

On 03/01/2021 02:45, Sreyan Chakravarty wrote:

Hi,

While building a live image via the livecd-creator I get the error
message which breaks the image building:

Error creating Live CD : resize2fs returned an error (1)!

Reading this BZ report :
https://bugzilla.redhat.com/show_bug.cgi?id=1602046


That BZ was written in 2018 and closed with WORKSFORME.  So it could not be 
duplicated.



Is there any way I can get my required versions ?

Why can't I downgrade ?


You are on F33, yes?  Well F33 was released with e2fsprogs-1.45.6-4.fc33 so 
there are no lower
versions available in the F33 repo.

If you really want an older version you can get it from

https://koji.fedoraproject.org/koji/packageinfo?packageID=231

---
The key to getting good answers is to ask good questions.
___
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-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: usb stick problem

[Tom Horsley]

On Sun, 3 Jan 2021 06:32:43 +0800
Ed Greshko wrote:

> One system here has USB-2 and USB-3 connections.  Even though a USB-3 should 
> downgrade to USB-2
> I've had a USB stick only work correctly in USB-2 slots.

I've got a system where most of the USB ports stopped working,
so even though the usb stick is the most common hardware problem,
usb ports can also be busted. Trying lots of different combinations
of things is usually best.
___
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-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: usb stick problem

[Ed Greshko]

On 03/01/2021 06:11, Matthew Miller wrote:

On Sat, Jan 02, 2021 at 11:48:00PM +0200, Kostas Sfakiotakis wrote:

Am trying to plug a usb memory stick onto my computer .

 From the looks of it , at first it looks that it gets recognized up
to a point , initially it gets asigned letter "f" /dev/sdf
but then some error pop up and i can't see it on dolphin or access
it somehow .

The attached files contains the relevant messages but i don't
understand what it says .

Well, it boils down to the errors saying the device isn't responding
properly. Are the contents of the stick important? I'd toss it into the
e-waste and get another.


I'd first plug it into a different USB slot.  If a desktop with front and rear 
connections I'd try an
opposite one.

One system here has USB-2 and USB-3 connections.  Even though a USB-3 should 
downgrade to USB-2
I've had a USB stick only work correctly in USB-2 slots.

---
The key to getting good answers is to ask good questions.
___
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-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Fedora 34 dns resolution problems?

[Michael H. Warfield]

I'm not even sure what to file a bug against.  This makes no sense to
me.

I have four Raspberry Pi's on Fedora 34.  One RPi4 and Three RPi3s, all
running aarch 64.  I also have numerous other RPi's on Fedora 33
aarch64 that are running just fine, parallel configurations.  I'm not
upgrading any of my X86_64 systems until I know the root cause of this.

If the Fedora 34 systems are up more than a day and I go to update I
get things like this...

-- 
rror: Curl error (6): Couldn't resolve host name for 
https://mirrors.fedoraproject.org/metalink?repo=fedora-modular-33=aarch64 
[Could not resolve host: mirrors.fedoraproject.org] 
(https://mirrors.fedoraproject.org/metalink?repo=fedora-modular-33=aarch64).
error: Curl error (6): Couldn't resolve host name for 
https://mirrors.fedoraproject.org/metalink?repo=fedora-modular-33=aarch64 
[Could not resolve host: mirrors.fedoraproject.org] 
(https://mirrors.fedoraproject.org/metalink?repo=fedora-modular-33=aarch64).
error: Curl error (6): Couldn't resolve host name for 
https://mirrors.fedoraproject.org/metalink?repo=fedora-modular-33=aarch64 
[Could not resolve host: mirrors.fedoraproject.org] 
(https://mirrors.fedoraproject.org/metalink?repo=fedora-modular-33=aarch64).
error: Curl error (6): Couldn't resolve host name for 
https://mirrors.fedoraproject.org/metalink?repo=fedora-modular-33=aarch64 
[Could not resolve host: mirrors.fedoraproject.org] 
(https://mirrors.fedoraproject.org/metalink?repo=fedora-modular-33=aarch64).
error: Curl error (6): Couldn't resolve host name for 
https://mirrors.fedoraproject.org/metalink?repo=fedora-modular-33=aarch64 
[Could not resolve host: mirrors.fedoraproject.org] 
(https://mirrors.fedoraproject.org/metalink?repo=fedora-modular-33=aarch64).
-- 

And this...

-- 
[mhw@rpi-plate ~]$ host mirrors.fedoraproject.org
mirrors.fedoraproject.org is an alias for wildcard.fedoraproject.org.
wildcard.fedoraproject.org has address 152.19.134.198
wildcard.fedoraproject.org has address 8.43.85.67
wildcard.fedoraproject.org has address 209.132.190.2
wildcard.fedoraproject.org has address 152.19.134.142
wildcard.fedoraproject.org has address 140.211.169.206
wildcard.fedoraproject.org has address 8.43.85.73
wildcard.fedoraproject.org has address 38.145.60.20
wildcard.fedoraproject.org has address 38.145.60.21
wildcard.fedoraproject.org has address 140.211.169.196
wildcard.fedoraproject.org has address 67.219.144.68
wildcard.fedoraproject.org has IPv6 address 2620:52:3:1:dead:beef:cafe:fed6
wildcard.fedoraproject.org has IPv6 address 2604:1580:fe00:0:dead:beef:cafe:fed1
wildcard.fedoraproject.org has IPv6 address 
2605:bc80:3010:600:dead:beef:cafe:fed9
wildcard.fedoraproject.org has IPv6 address 2620:52:3:1:dead:beef:cafe:fed7
wildcard.fedoraproject.org has IPv6 address 
2610:28:3090:3001:dead:beef:cafe:fed3
wildcard.fedoraproject.org has IPv6 address 
2605:bc80:3010:600:dead:beef:cafe:feda
[mhw@rpi-plate ~]$ ping mirrors.fedoraproject.org
ping: mirrors.fedoraproject.org: Name or service not known
[mhw@rpi-plate ~]$ ping6 mirrors.fedoraproject.org
ping6: mirrors.fedoraproject.org: Name or service not known

-- 

Checking /etc/resolv.conf looks good (host works) and nsswitch.conf
looks good.  Doesn't seem to depend on whether I use static name
servers or dhcp served name servers (I have some of each on both the
Fedora 34 and the Fedora 33).  All on the same network.  All with the
same name servers for resolution.

/etc/resolv.conf
-- 
# Generated by NetworkManager
search wittsend.com
nameserver 8.8.8.8
nameserver 1.1.1.1
nameserver 10.205.38.3
-- 

Restarting NetworkManager - no help

Rebooting the system restores normal operation for anywhere from
several hours to a day before it happens again.

WTH changed between 33 and 34 to create this problem?  Anybody got any
suggestions where to look?  None, I mean not a single solitary one of
my Fedora 33 systems, x86_64, arm7l (RPi 2's), or aarch64's are
behaving this way but all 4 of my Fedora 34 systems are.

Regards,
Mike
-- 
Michael H. Warfield (AI4NB) | (o) +1 706 850-8773 |  m...@wittsend.com
   /\/\|=mhw=|\/\/  | (c) +1 678 463-0932 |  
http://www.wittsend.com/mhw/
ARIN whois: MHW9-ARIN   | An optimist believes we live in the best of all
PGP Key: 0xC0EB9675674627FF | possible worlds.  A pessimist is sure of it!


signature.asc
Description: This is a digitally signed message part
___
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-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: usb stick problem

[Matthew Miller]

On Sat, Jan 02, 2021 at 11:48:00PM +0200, Kostas Sfakiotakis wrote:
> Am trying to plug a usb memory stick onto my computer .
> 
> From the looks of it , at first it looks that it gets recognized up
> to a point , initially it gets asigned letter "f" /dev/sdf
> but then some error pop up and i can't see it on dolphin or access
> it somehow .
> 
> The attached files contains the relevant messages but i don't
> understand what it says .

Well, it boils down to the errors saying the device isn't responding
properly. Are the contents of the stick important? I'd toss it into the
e-waste and get another.


-- 
Matthew Miller

Fedora Project Leader
___
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-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

usb stick problem

[Kostas Sfakiotakis]

Am trying to plug a usb memory stick onto my computer .

From the looks of it , at first it looks that it gets recognized up to 
a point , initially it gets asigned letter "f" /dev/sdf
but then some error pop up and i can't see it on dolphin or access it 
somehow .


The attached files contains the relevant messages but i don't understand 
what it says .


Can someone sched some light in it ??

[ 4014.282666] usb 8-1.2.2: new high-speed USB device number 8 using xhci_hcd
[ 4014.471968] usb 8-1.2.2: New USB device found, idVendor=090c, 
idProduct=2000, bcdDevice=11.00
[ 4014.471974] usb 8-1.2.2: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
[ 4014.471978] usb 8-1.2.2: Product: Disk 3.0
[ 4014.471981] usb 8-1.2.2: Manufacturer: USB
[ 4014.471984] usb 8-1.2.2: SerialNumber: CCYY25C13Z6U1L4B
[ 4014.476177] usb-storage 8-1.2.2:1.0: USB Mass Storage device detected
[ 4014.478683] scsi host8: usb-storage 8-1.2.2:1.0
[ 4015.582579] scsi 8:0:0:0: Direct-Access USB  Disk 3.0 1100 
PQ: 0 ANSI: 6
[ 4015.583068] sd 8:0:0:0: Attached scsi generic sg6 type 0
[ 4015.583210] sd 8:0:0:0: [sdf] 60825600 512-byte logical blocks: (31.1 
GB/29.0 GiB)
[ 4015.584674] sd 8:0:0:0: [sdf] Write Protect is off
[ 4015.584677] sd 8:0:0:0: [sdf] Mode Sense: 43 00 00 00
[ 4015.584838] sd 8:0:0:0: [sdf] Write cache: enabled, read cache: enabled, 
doesn't support DPO or FUA
[ 4015.594774]  sdf: sdf1
[ 4015.597594] sd 8:0:0:0: [sdf] Attached SCSI removable disk
[ 4045.899746] usb 8-1.2.2: reset high-speed USB device number 8 using xhci_hcd
[ 4051.516810] usb 8-1.2.2: device descriptor read/64, error -110
[ 4067.396181] usb 8-1.2.2: device descriptor read/64, error -110
[ 4067.676181] usb 8-1.2.2: reset high-speed USB device number 8 using xhci_hcd
[ 4067.853179] usb 8-1.2.2: device descriptor read/64, error -71
[ 4068.133239] usb 8-1.2.2: device descriptor read/64, error -71
[ 4068.412243] usb 8-1.2.2: reset high-speed USB device number 8 using xhci_hcd
[ 4068.412394] usb 8-1.2.2: Device not responding to setup address.
[ 4068.620061] usb 8-1.2.2: Device not responding to setup address.
[ 4068.827953] usb 8-1.2.2: device not accepting address 8, error -71
[ 4069.003956] usb 8-1.2.2: reset high-speed USB device number 8 using xhci_hcd
[ 4069.004171] usb 8-1.2.2: Device not responding to setup address.
[ 4069.21] usb 8-1.2.2: Device not responding to setup address.
4069.420041] usb 8-1.2.2: device not accepting address 8, error -71
[ 4069.420234] sd 8:0:0:0: [sdf] tag#0 FAILED Result: hostbyte=DID_TIME_OUT 
driverbyte=DRIVER_OK cmd_age=53s
[ 4069.420241] sd 8:0:0:0: [sdf] tag#0 CDB: Read(10) 28 00 03 a0 1f 80 00 00 08 
00
[ 4069.420246] blk_update_request: I/O error, dev sdf, sector 60825472 op 
0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[ 4069.420295] usb 8-1.2.2: USB disconnect, device number 8
[ 4069.423997] blk_update_request: I/O error, dev sdf, sector 60825472 op 
0x0:(READ) flags 0x0 phys_seg 8 prio class 0
[ 4069.424001] Buffer I/O error on dev sdf, logical block 60825472, async page 
read
[ 4069.424005] Buffer I/O error on dev sdf, logical block 60825473, async page 
read
[ 4069.424007] Buffer I/O error on dev sdf, logical block 60825474, async page 
read
[ 4069.424009] Buffer I/O error on dev sdf, logical block 60825475, async page 
read
[ 4069.424011] Buffer I/O error on dev sdf, logical block 60825476, async page 
read
[ 4069.424013] Buffer I/O error on dev sdf, logical block 60825477, async page 
read
[ 4069.424015] Buffer I/O error on dev sdf, logical block 60825478, async page 
read
[ 4069.424017] Buffer I/O error on dev sdf, logical block 60825479, async page 
read
[ 4069.644993] usb 8-1.2.2: new high-speed USB device number 9 using xhci_hcd
[ 4069.828273] usb 8-1.2.2: device descriptor read/64, error -71
[ 4070.108273] usb 8-1.2.2: device descriptor read/64, error -71
[ 4070.396059] usb 8-1.2.2: new high-speed USB device number 10 using xhci_hcd
[ 4070.572231] usb 8-1.2.2: device descriptor read/64, error -71
[ 4070.852210] usb 8-1.2.2: device descriptor read/64, error -71
[ 4070.956163] usb 8-1.2-port2: attempt power cycle
[ 4071.652027] usb 8-1.2.2: new high-speed USB device number 11 using xhci_hcd
[ 4071.652207] usb 8-1.2.2: Device not responding to setup address.
[ 4071.860167] usb 8-1.2.2: Device not responding to setup address.
___
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-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: btrfs RAID 5?

[Matthew Miller]

On Sat, Jan 02, 2021 at 12:55:20PM -0600, Richard Shaw wrote:
> From what I've been able to find online it doesn't look like RAID 5 is well
> supported by btrfs currently. Anyone have any data to the contrary?

As I understand it, that's still correct.

Personally, what I'd do with a three-drive setup is mirror two of them and
use the third for data where you don't care about redundancy (like a music
collection you have stored elsewhere).

-- 
Matthew Miller

Fedora Project Leader
___
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-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

btrfs RAID 5?

[Richard Shaw]

>From what I've been able to find online it doesn't look like RAID 5 is well
supported by btrfs currently. Anyone have any data to the contrary?

I have a 4TB media drive that's filling up and I'd like to add two more
disks to both increase capacity and add some redundancy. My understanding
is that if I did a 3 drive btrfs RAID 1 that I would just have 3 copies of
the same data and zero increased capacity.

Thanks,
Richard
___
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-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

How can I downgrade e2fsprogs ? resize2fs returned an error (1)!

[Sreyan Chakravarty]

Hi,

While building a live image via the livecd-creator I get the error
message which breaks the image building:

Error creating Live CD : resize2fs returned an error (1)!

Reading this BZ report :
https://bugzilla.redhat.com/show_bug.cgi?id=1602046

It recommends to downgrade e2fsprogs and other related packages to the
following versions:

e2fsprogs-1.43.8-2.fc28.x86_64.rpm
e2fsprogs-libs-1.43.8-2.fc28.x86_64.rpm
libcom_err-1.43.8-2.fc28.x86_64.rpm
libss-1.43.8-2.fc28.x86_64.rpm

Now I have tried :
dnf downgrade e2fsprogs

but that just errors out saying
Package e2fsprogs of lowest version already installed, cannot downgrade it.

I have also tried:
dnf install e2fsprogs-1.43.8-2.fc33.x86_64

but there seems to be no match:
No match for argument: e2fsprogs-1.43.8-2.fc33.x86_64
Error: Unable to find a match: e2fsprogs-1.43.8-2.fc33.x86_64

Is there any way I can get my required versions ?

Why can't I downgrade ?
-- 
Regards,
Sreyan Chakravarty
___
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-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: ERROR: installing 'ext4', when installing kernel-core-5.9.16-200.fc33.x86_64

[Sreyan Chakravarty]

On Sat, Jan 2, 2021 at 9:20 PM Sam Varshavchik  wrote:
>
> Chris Murphy writes:
>
> > On Sat, Jan 2, 2021, 1:23 AM Sreyan Chakravarty
> > sreya...@gmail.com> wrote:
> >
> >sort: fflush failed: 'standard output': Broken pipe
> >sort: write error
> >
> >gzip: stdout: Broken pipe
> >
> >gzip: stdout: Broken pipe
> >sort: write failed: 'standard output': Broken pipe
> >sort: write error
> >
> > ext4 is built-in so there is no kernel module for dracut to find.
>
> I noticed the above spam when "dnf upgrade" installed
> kernel-5.9.16-200.fc33.x86_64. I was wondering whether it'll boot, but it
> did.
>
> I don't recall seeing that come out when I upgraded to 5.9.15.
>
>

Don't know if it's a bug or just a crappy installer script.

-- 
Regards,
Sreyan Chakravarty
___
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-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: ERROR: installing 'ext4', when installing kernel-core-5.9.16-200.fc33.x86_64

[Sreyan Chakravarty]

On Sat, Jan 2, 2021 at 4:56 PM Chris Murphy  wrote:
>
>
> ext4 is built-in so there is no kernel module for dracut to find.
>

well then why try to install it ?

Is it the same case with the module sr_mod ?
-- 
Regards,
Sreyan Chakravarty
___
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-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: entropy generation

[Frank McCormick]

On 1/1/21 9:06 PM, Chris Murphy wrote:

On Fri, Jan 1, 2021 at 6:40 PM Frank McCormick  wrote:


Running Fedora 33 under systemd.

Lately my journal log has been spammed with hundreds of these lines:

Jan 01 20:26:56 localhost.localdomain rngd[645]: Entropy Generation is
slow, consider tuning/adding sources
Jan 01 20:26:56 localhost.localdomain rngd[645]: Entropy Generation is
slow, consider tuning/adding sources
Jan 01 20:26:56 localhost.localdomain rngd[645]: Entropy Generation is
slow, consider tuning/adding sources
Jan 01 20:26:56 localhost.localdomain rngd[645]: Entropy Generation is
slow, consider t

What can I do about this.


You can remove the rng-tools package if you want. It's being removed
in Fedora 34.

https://pagure.io/fedora-comps/c/1ae4e1840fd996445b47ab7a4adfa443eee48639?branch=master



Done. We'll see now what happens.

Thanks.



___
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-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Migration to btrfs: Is a reinstall the best way?

[Richard Shaw]

My plan is to upgrade from my current 500GB Samsung EVO to a 1TB version
and copy all my data over.

Creating the subvolumes and updating fstab is easy enough, but what else
needs to be done?

Would a reinstall do any "magic" that's difficult to do by hand?

Thanks,
Richard
___
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-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: ERROR: installing 'ext4', when installing kernel-core-5.9.16-200.fc33.x86_64

[Sam Varshavchik]

Chris Murphy writes:

On Sat, Jan 2, 2021, 1:23 AM Sreyan Chakravarty  
sreya...@gmail.com> wrote:


   sort: fflush failed: 'standard output': Broken pipe
   sort: write error

   gzip: stdout: Broken pipe

   gzip: stdout: Broken pipe
   sort: write failed: 'standard output': Broken pipe
   sort: write error

ext4 is built-in so there is no kernel module for dracut to find.


I noticed the above spam when "dnf upgrade" installed  
kernel-5.9.16-200.fc33.x86_64. I was wondering whether it'll boot, but it  
did.


I don't recall seeing that come out when I upgraded to 5.9.15.




pgpiUTy1XHvgi.pgp
Description: PGP signature
___
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-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Backing up Btrfs (was: btrfs or ext4)

[Patrick O'Callaghan]

Brief recap: I'm currently using BorgBackup, which among other things
does compression and deduplication. I'm looking at the pros and cons of
changing to Btrfs for backup (I already use it as my main fs). The
backup drives are currently ext4 so would need to be converted.

Now read on.

Following Chris Murphy's suggestion, I looked at:

https://fedoramagazine.org/btrfs-snapshots-backup-incremental/

My question is whether I can use compression and deduplication on the
backup even if these have not been enabled on the original fs. My
instinct is to say no, but I could be wrong.

poc

___
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-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: btrfs or ext4

[Patrick O'Callaghan]

On Fri, 2021-01-01 at 17:09 -0700, Chris Murphy wrote:
> > However it seems that Btrfs can do both these things, so
> > is there a case to be made for just setting it up that way, and
> > using
> > send and receive for the actual copying instead of Borg? It would
> > have
> > the advantage of making the backed-up files a little more
> > accessible
> > without special tools.
> 
> It's true. I use a variation on this article's approach:
> https://fedoramagazine.org/btrfs-snapshots-backup-incremental/
> 
> I can elaborate on that upon request, but probably start a new
> thread.

I'll start a thread.

> I haven't done so myself, but you could checkout btrbk

OK.

poc
___
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-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: ERROR: installing 'ext4', when installing kernel-core-5.9.16-200.fc33.x86_64

[Chris Murphy]

On Sat, Jan 2, 2021, 1:23 AM Sreyan Chakravarty  wrote:

> Hi,
>
> I am trying to create a livecd by using the livecd-creator.
>
> But whenever during the build process I get the error message:
>
> dracut: No '/dev/log' or 'logger' included for syslog logging
> dracut-install: ERROR: installing 'sr_mod'
> dracut-install: ERROR: installing 'ext4'
> sort: fflush failed: 'standard output': Broken pipe
> sort: write error
>
> gzip: stdout: Broken pipe
>
> gzip: stdout: Broken pipe
> sort: write failed: 'standard output': Broken pipe
> sort: write error
>
> I have tried to debug this via adding selinux-policy-targeted to my
> kickstart, but nothing changed.
>
> I have tried unpacking the scripts from
> kernel-core-5.9.16-200.fc33.x86_64.rpm to see what was going wrong,
> but I could see what was going wrong.
>
> rpm -q --scripts kernel-core-5.9.16-200.fc33.x86_64.rpm
>
> postinstall scriptlet (using /bin/sh):
> if [ `uname -i` == "x86_64" -o `uname -i` == "i386" ] &&
>[ -f /etc/sysconfig/kernel ]; then
>   /bin/sed -r -i -e
> 's/^DEFAULTKERNEL=kernel-smp$/DEFAULTKERNEL=kernel/'
> /etc/sysconfig/kernel || exit $?
> fi
>
> preuninstall scriptlet (using /bin/sh):
> /bin/kernel-install remove 5.9.16-200.fc33.x86_64
> /lib/modules/5.9.16-200.fc33.x86_64/vmlinuz || exit $?
> posttrans scriptlet (using /bin/sh):
> /bin/kernel-install add 5.9.16-200.fc33.x86_64
> /lib/modules/5.9.16-200.fc33.x86_64/vmlinuz || exit $?
>
>
> As you can see there is no dracut_install.
>
> Can anyone tell me where dracut_install is being called from ? What is
> going wrong here ?
>


ext4 is built-in so there is no kernel module for dracut to find.


--
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-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: entropy generation

[Chris Murphy]

On Fri, Jan 1, 2021, 7:14 PM Tom Horsley  wrote:

> On Fri, 1 Jan 2021 19:06:44 -0700
> Chris Murphy wrote:
>
> > You can remove the rng-tools package if you want. It's being removed
> > in Fedora 34.
>
> So where does random data come from in f34?



Kernel handles 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-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

ERROR: installing 'ext4', when installing kernel-core-5.9.16-200.fc33.x86_64

[Sreyan Chakravarty]

Hi,

I am trying to create a livecd by using the livecd-creator.

But whenever during the build process I get the error message:

dracut: No '/dev/log' or 'logger' included for syslog logging
dracut-install: ERROR: installing 'sr_mod'
dracut-install: ERROR: installing 'ext4'
sort: fflush failed: 'standard output': Broken pipe
sort: write error

gzip: stdout: Broken pipe

gzip: stdout: Broken pipe
sort: write failed: 'standard output': Broken pipe
sort: write error

I have tried to debug this via adding selinux-policy-targeted to my
kickstart, but nothing changed.

I have tried unpacking the scripts from
kernel-core-5.9.16-200.fc33.x86_64.rpm to see what was going wrong,
but I could see what was going wrong.

rpm -q --scripts kernel-core-5.9.16-200.fc33.x86_64.rpm

postinstall scriptlet (using /bin/sh):
if [ `uname -i` == "x86_64" -o `uname -i` == "i386" ] &&
   [ -f /etc/sysconfig/kernel ]; then
  /bin/sed -r -i -e
's/^DEFAULTKERNEL=kernel-smp$/DEFAULTKERNEL=kernel/'
/etc/sysconfig/kernel || exit $?
fi

preuninstall scriptlet (using /bin/sh):
/bin/kernel-install remove 5.9.16-200.fc33.x86_64
/lib/modules/5.9.16-200.fc33.x86_64/vmlinuz || exit $?
posttrans scriptlet (using /bin/sh):
/bin/kernel-install add 5.9.16-200.fc33.x86_64
/lib/modules/5.9.16-200.fc33.x86_64/vmlinuz || exit $?


As you can see there is no dracut_install.

Can anyone tell me where dracut_install is being called from ? What is
going wrong here ?

My flattened kickstart file:
https://pastebin.com/raw/B5Ph4Rbw
-- 
Regards,
Sreyan Chakravarty
___
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-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org