Playing with the version-changer for v2 logs, I hit this -
If the log sync code gets a log sunit of 0, we get an oops.
Glen has this bit of "defensive programming" in irix as well, to make
sure we never get a sunit of 0 - bump it to 1 if we see it.
Seems like this could go in the mount path instead of the log sync
path, but Glen seemed to remember finding a reason that it won't work
that way. Who am I to argue? :)
Date: Thu Aug 15 11:53:36 PDT 2002
Workarea:
stout.americas.sgi.com:/localhome/src/sandeen/2.4.x-xfs/workarea-alwaysclean
The following file(s) were checked into:
bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs
Modid: 2.4.x-xfs:slinx:125188a
linux/fs/xfs/xfs_log.c - 1.253
- Make sure we never get a 0 sunit - things go badly if this happens.
Use "1" for "no sunit"
|