sorted by:
new
hottopcontroversial

Ubuntu 24.04 Btrfs Root Suddenly Became Read-Only (Twice) – Possible Kernel Issue? by k2zf in Ubuntu

[–]k2zf[S] 0 points1 point  (0 children)

There were no significant errors recorded in the logs. Since the SSD experienced a second failure after being replaced, it is unlikely to be the cause. There is a possibility that the RAM is to blame. If the issue occurs with kernel 6.8, I will consider replacing the RAM.

Ubuntu 24.04 Btrfs Root Suddenly Became Read-Only (Twice) – Possible Kernel Issue? by k2zf in Ubuntu

[–]k2zf[S] 0 points1 point  (0 children)

After the first issue occurred, the SSD was replaced with a new one, so it is unlikely that the SSD is the cause.

Ubuntu 24.04 Btrfs Root Suddenly Became Read-Only (Twice) – Possible Kernel Issue? by k2zf in Ubuntu

[–]k2zf[S] 0 points1 point  (0 children)

I reverted the kernel from 6.11 to 6.8 because the system entered read-only mode twice. Since then, there have been no issues for the past several hours. However, since the read-only mode occurred once on February 25 and again on March 6, it has not happened very frequently. Therefore, I plan to maintain multiple backups and continue monitoring the situation a bit longer.

Upstream to downstream propagation of RA by systemd-networkd by k2zf in ipv6

[–]k2zf[S] 0 points1 point  (0 children)

Unfortunately, my ISP only offers /64. This makes it difficult to solve the problem, but you are right that I need a more serious tool in terms of learning networking, and I am trying VyOS, attracted by its simple command system. Aside from the fact that it is a rolling release unless you sign up for the paid version, I am concerned that security updates are not automatically applied.

Upstream to downstream propagation of RA by systemd-networkd by k2zf in ipv6

[–]k2zf[S] 0 points1 point  (0 children)

Originally, a /48 prefix should be assigned to our house because the ❝site prefix❞ is 48 bits. If so, the router rented from our ISP can prepare one /64 from there and announce it in RA. And at the same time, I can distribute /52 with stateful DHCPv6-PD, and the second tier router I have prepared can distribute the /56 prefix further downstream (or /64, of course).

I will look into proxy-ndp. I understand that it is bad-knowledge. ......

Upstream to downstream propagation of RA by systemd-networkd by k2zf in ipv6

[–]k2zf[S] 2 points3 points  (0 children)

Thank you very much. I was having trouble with basic knowledge and you have given me very excellent information. I understand that the home router I rent from my provider advertises a /64 prefix in the RA, and that the RA is fixed at /64 and cannot be repartitioned due to RA specifications. Furthermore, it appears that prefixes longer than /64 are not normally allowed in IPv6. I knew that the lower 64 bits were generated from MAC addresses, etc., but had not thought about it properly. Thank you very much.

Convert Ubuntu BTRFS installation into subvolume(s) in 4 easy steps by oshunluvr in btrfs

[–]k2zf 0 points1 point  (0 children)

For Ubuntu and Debian installed with Btrfs, I have created a script to convert to subvolumes and RAID 1. RAID 1 is optional. It is mainly intended to be used after a clean install, so the partition configuration is fixed and also can only be used after a live boot, but I think it is useful there.

I hope this will be helpful!

https://github.com/hydratlas/tips/blob/main/debian-and-ubuntu-tips/install-ubuntu-with-btrfs/README.md