save.dat file checker

[Rava]

You ever used Windows 10 or 11?

No, and hopefully I never have to.

I've never encountered a single time Windows changed the access right of any partition before either, until now.

I see, but Linux folk will still try to get it running with ext3/4 partitions, and aside it all, it is your right to use whatever OS and whatever partition you want to, it is your hardware (including the harddisc), not the property of SM-Witless.
Seems it is time for a lawsuit - free software users vs Mickysoft.

[Ed_P]

Another thing to note, this access problem never showed up with RC3 and I've had this notebook since last Christmas. The nightly plugged in/not plugged in, Windows/Porteus running, lid closed has occurred before, but now the write problem.

But since I now know how it occurs and how to get around it it's more a pita than a big problem.

Added in 37 minutes 10 seconds:

fsck cheatcode.

Maybe not.

Code: Select all

guest@porteus:~$ su
Password: 
root@porteus:/home/guest# fsck /mnt/nvme0n1p7/porteus5.0/changes/50save.dat
fsck from util-linux 2.37.4
If you wish to check the consistency of an XFS filesystem or
repair a damaged filesystem, see xfs_repair(8).
root@porteus:/home/guest# 

Code: Select all

root@porteus:/home/guest# xfs_repair(8)
bash: syntax error near unexpected token `8'
root@porteus:/home/guest# xfs_repair /mnt/nvme0n1p7/porteus5.0/changes/50save.dat
Cannot get host filesystem geometry.
Repair may fail if there is a sector size mismatch between
the image and the host filesystem.
Phase 1 - find and verify superblock...
Cannot get host filesystem geometry.
Repair may fail if there is a sector size mismatch between
the image and the host filesystem.
Phase 2 - using internal log
        - zero log...
        - scan filesystem freespace and inode maps...
        - found root inode chunk
Phase 3 - for each AG...
        - scan and clear agi unlinked lists...
        - process known inodes and perform inode discovery...
        - agno = 0
        - agno = 1
        - agno = 2
        - agno = 3
        - process newly discovered inodes...
Phase 4 - check for duplicate blocks...
        - setting up duplicate extent list...
        - check for inodes claiming duplicate blocks...
        - agno = 0
        - agno = 2
        - agno = 1
        - agno = 3
Phase 5 - rebuild AG headers and trees...
        - reset superblock...
Phase 6 - check inode connectivity...
        - resetting contents of realtime bitmap and summary inodes
        - traversing filesystem ...
        - traversal finished ...
        - moving disconnected inodes to lost+found ...
Phase 7 - verify and correct link counts...
done
root@porteus:/home/guest# 

[Rava]

repair a damaged filesystem, see xfs_repair(8).

I think it means "man xfs_repair" in "man section 8", and not "xfs_repair(8)" - but there seems to be no such thing:

Code: Select all

                                     Linux Manpages Online - man.cx manual pages
   [INS: :INS]

                                    Manpages

   Manpage: ____________________ go

Search results for fxs_repair

   A splitbrain.org Service | Back to top

is what you get when executing "man fxs_repair".
Anyhow, fxs_repair doesn't know "--help" nor "-h" but executing without any parameters does the trick:

Code: Select all

root@porteus:/# xfs_repair 
Usage: xfs_repair [options] device

Options:
  -f           The device is a file
  -L           Force log zeroing. Do this as a last resort.
  -l logdev    Specifies the device where the external log resides.
  -m maxmem    Maximum amount of memory to be used in megabytes.
  -n           No modify mode, just checks the filesystem for damage.
               (Cannot be used together with -e.)
  -P           Disables prefetching.
  -r rtdev     Specifies the device where the realtime section resides.
  -v           Verbose output.
  -c subopts   Change filesystem parameters - use xfs_admin.
  -o subopts   Override default behaviour, refer to man page.
  -t interval  Reporting interval in seconds.
  -d           Repair dangerously.
  -e           Exit with a non-zero code if any errors were repaired.
               (Cannot be used together with -n.)
  -V           Reports version and exits.

[Ed_P]

executing without any parameters does the trick:

Yup.