[systemd-devel] where systemd gets list of fsck targets?

[Vratislav Podzimek]

On Thu, 2011-06-09 at 11:12 +0200, Michal Schmidt wrote:
> On Fri, 2011-06-03 at 10:39 +0200, Vratislav Podzimek wrote:
> > Hi,
> > I have a problem with systemd-fsck running on every boot on partition
> > not specified in /etc/fstab nor having .mount unit file. How can I fix
> > it? Where systemd gets information about which partitions to run fsck
> > on?
> 
> Is there a corresponding fsck at ....service listed?:
> systemctl --all --full | grep ^fsck
with 2>&1 added it gives:
  fsck-root.service
  fsck at dev-disk-by\x2duuid-SOME_UUID.service loaded inactive dead
where SOME_UUID is the uuid of of my /boot partition (so nothing about
the one unintentionally checked on boot)
> 
> If it is, what does this say about it?:
> systemctl show 'fsck at ....service'
on beforementioned fsck at dev-disk-by...service gives this (uuid is the
uuid of my /boot partition):

Id=fsck at dev-disk-by\x2duuid-7d9e9d8a\x2d411f\x2d4202\x2da77d
\x2d9d2058b3e246.service
Names=fsck at dev-disk-by\x2duuid-7d9e9d8a\x2d411f\x2d4202\x2da77d
\x2d9d2058b3e246.service
Requires=systemd-logger.socket
BindTo=dev-disk-by\x2duuid-7d9e9d8a\x2d411f\x2d4202\x2da77d
\x2d9d2058b3e246.device
RequiredBy=boot.mount
Before=boot.mount shutdown.target
After=systemd-readahead-collect.service systemd-readahead-replay.service
dev-disk-by\x2duuid-7d9e9d8a\x2d411f\x2d4202\x2da77d
\x2d9d2058b3e246.device systemd-logger.socket fsck-root.service
Description=File System Check
on /dev/disk/by-uuid/7d9e9d8a-411f-4202-a77d-9d2058b3e246
LoadState=loaded
ActiveState=inactive
SubState=dead
FragmentPath=/lib/systemd/system/fsck at .service
InactiveExitTimestamp=Thu, 09 Jun 2011 11:31:55 +0200
InactiveExitTimestampMonotonic=674457813
ActiveEnterTimestampMonotonic=0
ActiveExitTimestampMonotonic=0
InactiveEnterTimestamp=Thu, 09 Jun 2011 11:31:55 +0200
InactiveEnterTimestampMonotonic=674699555
CanStart=yes
CanStop=yes
CanReload=no
CanIsolate=no
StopWhenUnneeded=no
RefuseManualStart=no
RefuseManualStop=no
AllowIsolate=no
DefaultDependencies=no
OnFailureIsolate=no
IgnoreOnIsolate=no
DefaultControlGroup=name=systemd:/system/fsck at .service/dev-disk-by
\x2duuid-7d9e9d8a\x2d411f\x2d4202\x2da77d\x2d9d2058b3e246
ControlGroup=cpu:/system/fsck at .service/dev-disk-by\x2duuid-7d9e9d8a
\x2d411f\x2d4202\x2da77d\x2d9d2058b3e246
name=systemd:/system/fsck at .service/dev-disk-by\x2duuid-7d9e9d8a\x2d411f
\x2d4202\x2da77d\x2d9d2058b3e246
NeedDaemonReload=no
JobTimeoutUSec=0
ConditionTimestamp=Thu, 09 Jun 2011 11:31:55 +0200
ConditionTimestampMonotonic=674444353
ConditionResult=yes
Type=oneshot
Restart=no
NotifyAccess=none
RestartUSec=100ms
TimeoutUSec=0
ExecStart={ path=/lib/systemd/systemd-fsck ;
argv[]=/lib/systemd/systemd-fsck %f ; ignore=no ; start_time=[n/a] ;
stop_time=[Thu, 09 Jun 2011 11:31:55 +0200] ; pid=1500 ; code=exited ;
status=0 }
UMask=0002
LimitCPU=18446744073709551615
LimitFSIZE=18446744073709551615
LimitDATA=18446744073709551615
LimitSTACK=18446744073709551615
LimitCORE=18446744073709551615
LimitRSS=18446744073709551615
LimitNOFILE=1024
LimitAS=18446744073709551615
LimitNPROC=7879
LimitMEMLOCK=65536
LimitLOCKS=18446744073709551615
LimitSIGPENDING=7879
LimitMSGQUEUE=819200
LimitNICE=0
LimitRTPRIO=0
LimitRTTIME=18446744073709551615
OOMScoreAdjust=0
Nice=0
IOScheduling=0
CPUSchedulingPolicy=0
CPUSchedulingPriority=0
TimerSlackNSec=50000
CPUSchedulingResetOnFork=no
NonBlocking=no
StandardInput=null
StandardOutput=syslog+console
StandardError=inherit
SyslogPriority=30
SyslogLevelPrefix=yes
SecureBits=0
CapabilityBoundingSet=18446744073709551615
MountFlags=1048576
PrivateTmp=no
SameProcessGroup=no
KillMode=control-group
KillSignal=15
PermissionsStartOnly=no
RootDirectoryStartOnly=no
RemainAfterExit=no
GuessMainPID=yes
ExecMainStartTimestampMonotonic=0
ExecMainExitTimestampMonotonic=0
ExecMainPID=1500
ExecMainCode=1
ExecMainStatus=0
MainPID=0
ControlPID=0
SysVStartPriority=-1
FsckPassNo=2

So I can see no line mentioning the partition unintentionallychecked on
boot

Vratislav Podzimek