On Fri, 2023-07-14 at 10:58 -0700, Samuel Sieb wrote:
On 7/14/23 10:49, Patrick O'Callaghan wrote:
> On Fri, 2023-07-14 at 09:49 -0700, Samuel Sieb wrote:
> > On 7/14/23 03:44, Patrick O'Callaghan wrote:
> > > On Thu, 2023-07-13 at 15:37 -0700, Samuel Sieb wrote:
> > > > On 7/13/23 14:39, Patrick O'Callaghan wrote:
> > > > > So I followed that (i.e. applied 'restorecon -v /SWAP',
> > > > > where
> > > > > /SWAP
> > > > > is
> > > > > a Btrfs subvolume holding the swapfile, but it still fails
> > > > > with
> > > > > the
> > > > > same error, i.e.:
> > > >
> > > > Did you check what the label on it was after that?
> > >
> > > Yes:
> > >
> > > # findmnt -no UUID -T /SWAP/swapfile
> > > 8e1f7af4-c0bf-434e-b1c4-a9af2c810d56
> > > [root@Bree ~]# btrfs inspect-internal map-swapfile -r
> > > /SWAP/swapfile
> > > 472549965
> > > # cat /proc/cmdline
> > > BOOT_IMAGE=(hd2,gpt2)/vmlinuz-6.3.12-200.fc38.x86_64
> > > root=UUID=8e1f7af4-c0bf-434e-b1c4-a9af2c810d56 ro
> > > rootflags=subvol=root modprobe.blacklist=i915 rd.blacklist=i915
> > > vconsole.font=latarcyrheb-sun16 rhgb quiet audit=0
> > > resume=UUID=8e1f7af4-c0bf-434e-b1c4-a9af2c810d56
> > > resume_offset=472549965
> >
> > Where do you show the selinux label anywhere in that?
> > "ls -lZ"
>
> $ ls -lZ /SWAP/swapfile
> -rw-------. 1 root root unconfined_u:object_r:default_t:s0
> 34359738368 Jul 12 12:46 /SWAP/swapfile
I pressed send too quickly. "ls -alZ /SWAP"
# ls -lZ /SWAP
total 33554436
-rw-r--r--. 1 root root unconfined_u:object_r:unlabeled_t:s0 329 Jul 13 22:32
README [just my notes - poc]
-rw-------. 1 root root unconfined_u:object_r:default_t:s0 34359738368 Jul 12 12:46
swapfile
and just in case:
[root@Bree ~]# ls -lZd /SWAP
drwxr-xr-x. 1 root root system_u:object_r:default_t:s0 28 Jul 13 22:32 /SWAP
Do you have the selinux error message?
As I've mentioned, the only error is in the journal:
Jul 14 22:10:37 Bree systemd-sleep[51364]: Failed to find location to hibernate to:
Permission denied
Jul 14 22:10:37 Bree systemd[1]: systemd-hibernate.service: Main process exited,
code=exited, status=1/FAILURE
I'm guessing it's an SElinux issue, since it goes away when SElinux is
off.
poc