Re:procparbreastions and fdisk
What did you do. Resize parbreastions? If so, did you also resize the filesystems inside? Check specifically the windows filessystem sizes.
Default maximum parbreastion number is 15 IIRC, as the kernel view appears to be. Although you can still make an sda4.
They only disagree on sda12 (fdisk) so I suggest you delete that one. fdisk appaers to think it is one big parbreastion,proc-parbreastions, ie the kernel view on the disk sees sda12 to sda15. How the discrepancy started I have no idea, but this looks like an unstable situation to me.
what do tools like sfdisk, cfdisk and parted have to say about it?
For future attempts: Use only one parbreastioning tool on a table. I don't care which one, but stick to it.
Hi, several times, a Job is in state active, but nothing seems to happen (I've no access to the printer so I can't tell wats going on there) Is...
It is a shuffled table (parbreastions not in correct order), though no obvious errors are visible. The shuffling can be fixed easily with sfdisk, but I wouldn't mess with it until you made a backup of all important data.
neither is correct I would say. So delete all parbreastion(s) in the space of sda12 and redo the parbreastioning. Keep the limit of 15 parbreastions in mind.
Eric
cups job is "active" but nothing seems to happen
Linux groups from Newsgroups