From Newsgroup: alt.os.linux.ubuntu

On Sun, 09 Feb 2025 11:50:53 -0500, "David W. Hodgins" <dwhodgins@nomail.afraid.org> wrote in <op.21pnq3q6a3w0dxdave@hodgins.homeip.net>:

On Sun, 09 Feb 2025 01:11:45 -0500, Jasen Betts
<usenet@revmaps.no-ip.org> wrote:

On 2025-02-05, pinnerite <pinnerite@gmail.com> wrote:

I need to be able to identify the partition address and its file
address, particularly when I have two drives on-line.

I tried a variety of live devices. Antix was the only one that came
close.

But years ago I remember a file manager that would allow the user to
use a single click to switch the contents of the address line at the
top from say /home/fred to /dev/sdb2 or back. I could not re-locate
it.

Does this strike a chord?

assuming you don't actually mean /dev/sdb2 which is a block device, not
a mounted file system.

Nautilus, has backwards, forwards, bookmarks, and tabs. It's the
standard GNOME file-manager. For some reason GNOME call it "Files"

I suspect it is /dev/sdb2 being referred to, for the purpose of making
sure it's backed up etc.

With complicated filesystem layouts, it's easy to forget what is where.

I vaguely remember a gui file manager that had the device as an optional column. For the amount of time I needed it, I considered it a waste of
screen space, so didn't use it and don't remember which file manager had
it.

I have a file called default.gpfl in my home directory. Assuming I want
to find out what device it's on ...

$ stat /home/dave/default.gpfl | grep ^Dev Device: 259,11 Inode:
5411522 Links: 1

To find out what device 259,11 is replace the comma with a colon and
preface it with "/sys/dev/block/".

$ ls -l /sys/dev/block/259:11 lrwxrwxrwx 1 root root 0 Feb 8 19:33 /sys/dev/block/259:11 -> ../../devices/pci0000:00/0000:00:02.4/0000:05:00.0/nvme/nvme1/nvme1n1/

nvme1n1p7/

So it's /dev/nvme1n1p7 that would need to work with to ensure the file /home/dave/default.gpfl was included.

On my system currently ...
$ mount|grep nvme1n1p7 /dev/nvme1n1p7 on /data type ext4 (rw,relatime)

I didn't put /home on a separate file system in this install when I
created it as it was just a test installation. I moved it later and
replaced it with a symlink ...
$ ls -l / | grep home lrwxrwxrwx 1 root root 10 Dec 14 12:17 home

/data/home/

$ mount | grep ' / '
/dev/ on / type ext4 (rw,relatime)

With /home having been moved, anyone looking at just the mount command
output would think files in /home/dave were in nvme1n1p8, not nvme1n1p7.

This was one of the test installs till my main computer died. I then
used my backup to restore my data into this install.

Regards, Dave Hodgins

One can also run "df" on the directory in question, and it
will tell you what the device is:

_[/srv/Extreme_Pro]_(xxx@lm)🐧_
$ df .
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda1 3844518728 862344652 2786808504 24% /srv/Extreme_Pro
--
-v
--- Synchronet 3.20c-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.ubuntu

On Thu, 13 Feb 2025 04:05:33 -0000 (UTC)
William Unruh <unruh@invalid.ca> wrote:

On 2025-02-11, pinnerite <pinnerite@gmail.com> wrote:

On Sun, 09 Feb 2025 16:14:22 -0500
"David W. Hodgins" <dwhodgins@nomail.afraid.org> wrote:

On Sun, 09 Feb 2025 13:55:36 -0500, vallor <vallor@cultnix.org> wrote:
<snip>

One can also run "df" on the directory in question, and it
will tell you what the device is:

_[/srv/Extreme_Pro]_(xxx@lm)🐧_
$ df .
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda1 3844518728 862344652 2786808504 24% /srv/Extreme_Pro

Lol. Thanks. That's one I did not know.

I now realize I had never bothered using "page down" while viewing the df man page.

Regards, Dave Hodgins

My arrangement is not that simple.

My system is installed on a 1TB nvMe.
But all my data is on a separate partition on a 2TB hard drive

/home/Data The backup only has two partitions: Data and Mythtv so

just rsyncing from /dev/sda to /dev/sdb won't do it.

You would never rsync from /dev/sda to /dev/sdb. they are not
directories and files. You would mount /dev/sda1 and /dev/sdb1 say and then rsync between those mounted filesystems. (call them SDA and SDB if you want.)sda and sdb are the whole disk. sda# are partitions on sda where # means some number . But you do not have drives sda or sdb You have
driver /dev/nvme0 and /dev/nvme1 say, with partitions like nvme0n1p2

Mount the partitions into your root filessytem and then you can rsync
between those mounted partitions.

Of course I have to mount them but I have to identify them first!

Anyway, running Antix looks like a temporary solution.

I copied the script that mounts the partitions to Antix /media/EFU-LIVE
but when I tried to execute it, it was not recognised.
I could not chmod it to make it executable. When I tried to do so by right-clicking it and checking the execute boxes, the result wouldn't hold. I am not giving up.

Fortunately I can still back up to a second machine.

I hope I can organise persistence so that I can save a script toi the flash drive.

Regards, Alan

--
Linux Mint 21.3 kernel version 5.15.0-131-generic Cinnamon 6.0.4
AMD Ryzen 7 7700, Radeon RX 6600, 32GB DDR5, 1TB SSD, 2TB Barracuda
--- Synchronet 3.20c-Linux NewsLink 1.2