cannot rollback any channel because the peer contains channe

Error message

cannot rollback any channel because the peer contains channel(s) %s that were bootstrapped from snapshot

What it means

RollbackKVLedger refuses to roll back when the peer contains any ledger bootstrapped from a snapshot. Rollback rewinds to an earlier block number, which is meaningless and unsafe for snapshot-bootstrapped channels (their earliest local data is the snapshot point, not genesis). The error names the affected channels.

Source

Thrown at core/ledger/kvledger/rollback.go:31

)

// RollbackKVLedger rollbacks a ledger to a specified block number
func RollbackKVLedger(rootFSPath, ledgerID string, blockNum uint64) error {
	fileLockPath := fileLockPath(rootFSPath)
	fileLock := leveldbhelper.NewFileLock(fileLockPath)
	if err := fileLock.Lock(); err != nil {
		return errors.Wrap(err, "as another peer node command is executing,"+
			" wait for that command to complete its execution or terminate it before retrying")
	}
	defer fileLock.Unlock()

	blockstorePath := BlockStorePath(rootFSPath)
	ledgerIDs, err := blkstorage.GetLedgersBootstrappedFromSnapshot(blockstorePath)
	if err != nil {
		return errors.WithMessage(err, "error while checking if any ledger has been bootstrapped from snapshot")
	}
	if len(ledgerIDs) > 0 {
		return errors.Errorf("cannot rollback any channel because the peer contains channel(s) %s that were bootstrapped from snapshot", ledgerIDs)
	}

	if err := blkstorage.ValidateRollbackParams(blockstorePath, ledgerID, blockNum); err != nil {
		return err
	}

	logger.Infof("Dropping databases")
	if err := dropDBs(rootFSPath); err != nil {
		return err
	}

	logger.Info("Rolling back ledger store")
	indexConfig := &blkstorage.IndexConfig{AttrsToIndex: attrsToIndex}
	if err := blkstorage.Rollback(blockstorePath, ledgerID, blockNum, indexConfig); err != nil {
		return err
	}
	logger.Infof("The channel [%s] has been successfully rolled back to the block number [%d]", ledgerID, blockNum)
	return nil

View on GitHub (pinned to 2736b63f8f)

Solutions

Do not roll back channels bootstrapped from a snapshot; the command is blocked by design.
To recover a snapshot-joined channel, rejoin it from a newer snapshot taken before the bad state.
For genesis-bootstrapped channels on the same peer, temporarily migrate the snapshot channels to another peer, or accept the restriction.
Always verify which channels are snapshot-bootstrapped before planning rollback procedures.

Example fix

// before
peer node rollback --channelID mychannel --blockNumber 100
// Error: cannot rollback any channel because the peer contains channel(s) [mychannel] that were bootstrapped from snapshot
// after: rejoin channel from an earlier snapshot
peer node channel join --snapshot-file /var/snapshots/before-fork.snapshot

Defensive patterns

Strategy: validation

Validate before calling

// pre-check before planning a rollback
ids, err := blkstorage.GetLedgersBootstrappedFromSnapshot(blkstorage.BlockStorePath(rootFSPath))
if err != nil {
	return err
}
if len(ids) > 0 {
	return fmt.Errorf("rollback unsupported for snapshot-bootstrapped channels: %v", ids)
}

Try / catch

if err := ledger.RollbackKVLedger(rootFSPath, ledgerID, blockNum); err != nil {
	if strings.Contains(err.Error(), "bootstrapped from snapshot") {
		return fmt.Errorf("recover via rejoin from an earlier snapshot: %w", err)
	}
	return err
}

Prevention

Maintain a periodic snapshot schedule for snapshot-joined channels so recovery points exist
Check channel bootstrap type before including channels in rollback procedures
Do not mix genesis and snapshot recovery playbooks on the same peer
Validate rollback parameters (target blockNum exists) only for genesis-bootstrapped channels

When it happens

Trigger: Running 'peer node rollback' targeting (or while the peer hosts) channels joined from a snapshot, detected via blkstorage.GetLedgersBootstrappedFromSnapshot before parameter validation.

Common situations: Rolling back after a fork on a peer where some channels were snapshot-joined; applying a rollback runbook written for genesis-bootstrapped peers.

Related errors

AI-assisted analysis of hyperledger/fabric@2736b63f8f (2026-09-04). Data as JSON: /api/errors/52bc7c1a23e04115. Report an issue: GitHub.